intel-device-plugins-for-kubernetes
k8s-gitops
Our great sponsors
| intel-device-plugins-for-kubernetes | k8s-gitops | |
|---|---|---|
| 6 | 4 | |
| 448 | 602 | |
| 2.7% | - | |
| 9.4 | 9.9 | |
| 5 days ago | 5 days ago | |
| Go | Shell | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
intel-device-plugins-for-kubernetes
-
Plex on Kubernetes with intel iGPU passthrough - Small how to
Install the Intel Device Plugin Operator: More information on this can be found at https://github.com/intel/intel-device-plugins-for-kubernetes/blob/main/cmd/operator/README.md. I highly recommend installing this operator via the Helm chart available here: https://github.com/intel/helm-charts/tree/main/charts/device-plugin-operator.
-
So Intel nucs self replicate….gotta love eBay. New 8gen Nuc.
GPU Plugin for Kubernetes: https://github.com/intel/intel-device-plugins-for-kubernetes/blob/main/cmd/gpu_plugin/README.md
-
How can Intel quick sync be exposed to a pod?
Same thing for the GPU plugin — https://github.com/intel/intel-device-plugins-for-kubernetes
k8s-gitops
-
How can Intel quick sync be exposed to a pod?
And then deploy Plex or other service to the node based on the label that is created — https://github.com/billimek/k8s-gitops/blob/master/default/plex/plex.yaml#L60-L62
No prob! So the NFD config needs to know the pci ids for what you’re looking to label. The values are here: https://github.com/billimek/k8s-gitops/blob/master/kube-system/node-feature-discovery/node-feature-discovery.yaml#L67-L71
So this one https://github.com/billimek/k8s-gitops/blob/master/kube-system/intel-gpu_plugin/intel-gpu_plugin.yaml is a custom yaml that deploys the Intel plugin as a daemonset but only on nodes that have the label "feature.node.kubernetes.io/custom-intel-gpu".
What are some alternatives?
truecharts - Community App Catalog for TrueNAS SCALE [Moved to: https://github.com/truecharts/charts]
node-feature-discovery - Node feature discovery for Kubernetes
smarter
flux2-kustomize-helm-example - A GitOps workflow example for multi-env deployments with Flux, Kustomize and Helm.
otomi-core - Self-hosted DevOps PaaS for Kubernetes
velero-plugin-for-aws - Plugins to support Velero on AWS
cloud-native-platform - Repo for "How to build your own cloud-native platform on IaaS clouds in 2021"
csi-driver-smb - This driver allows Kubernetes to access SMB Server on both Linux and Windows nodes.
k3d-action - A GitHub Action to run lightweight ephemeral Kubernetes clusters during workflow. Fundamental advantage of this action is a full customization of embedded k3s clusters. In addition, it provides a private image registry and multi-cluster support.
Zenko - Zenko is the open source multi-cloud data controller: own and keep control of your data on any cloud.
tekton-pipeline-and-task-test - This Demo repository will deploy and configure a Tekton CI System. It uses GitHub Actions to validate the Tekton config on every commit.
serverless-vault-with-cloud-run - Guide to running Vault on Cloud Run