vsphere-csi-driver
sriov-network-device-plugin
vsphere-csi-driver | sriov-network-device-plugin | |
---|---|---|
6 | 3 | |
278 | 368 | |
3.2% | 2.2% | |
9.3 | 7.4 | |
1 day ago | 12 days ago | |
Go | Go | |
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.
vsphere-csi-driver
-
Understanding Kubernetes Limits and Requests
As we covered in our "What's new in Kubernetes 1.19" article, the CSI driver for vSphere has been stable for some time. Now, all plugin operations for vspherevolume are now redirected to the out-of-tree 'csi.vsphere.vmware.com' driver.
-
Default Grafana K8s app PV issue: FailedBinding persistentvolume-controller no persistent volumes available for this claim and no storage class is set
Take a look at https://github.com/kubernetes-sigs/vsphere-csi-driver as well as the stuff the other person mentioned.
-
Which one of the two big FOSS RDBMS work best with .Net? MySQL or PostgreSQL?
Regarding your question about persistent storage: as I'm running in an on-prem environment I'm using VMware vSphere CSI to integrate our common storage infrastructure but I've to admin that I wasn't aware of OpenEBS even though I don't think that this is something I would need right now.
- Serving up storage to docker containers.
-
[HELP] VSphere CSI Driver on OK failing versus installed on OCP?
For your issues with the CSI on OK, please log and issue here, the engineering team do check this github repo https://github.com/kubernetes-sigs/vsphere-csi-driver
sriov-network-device-plugin
-
Understanding Kubernetes Limits and Requests
This framework allows the use of external devices (e.g., NVIDIA GPUs, AMD GPUS, SR-IOV NICs) without modifying core Kubernetes components.
-
kubernetes networking model
[4] sriov network
-
Multicast in a Container
Your best option, if the other options do not fit your need, is SR-IOV. If your NIC supports it, it will basically split your NIC into "N" interfaces, you can then pass one of those to your container. Here's an example, again for k8s. https://github.com/k8snetworkplumbingwg/sriov-network-device-plugin
What are some alternatives?
rook - Storage Orchestration for Kubernetes
cilium - eBPF-based Networking, Security, and Observability
blob-csi-driver - Azure Blob Storage CSI driver
k3s - Lightweight Kubernetes
okd - The self-managing, auto-upgrading, Kubernetes distribution for everyone
danm - TelCo grade network management in a Kubernetes cluster
cloud-provider - cloud-provider defines the shared interfaces which Kubernetes cloud providers implement. These interfaces allow various controllers to integrate with any cloud provider in a pluggable fashion. Also serves as an issue tracker for SIG Cloud Provider.
website - Kubernetes website and documentation repo:
cloud-provider-openstack
k8s-device-plugin - Kubernetes (k8s) device plugin to enable registration of AMD GPU to a container cluster
cluster-api-provider-vsphere
k9s - 🐶 Kubernetes CLI To Manage Your Clusters In Style!