external-provisioner
Sidecar container that watches Kubernetes PersistentVolumeClaim objects and triggers CreateVolume/DeleteVolume against a CSI endpoint (by kubernetes-csi)
sig-storage-local-static-provisioner
Static provisioner of local volumes (by kubernetes-sigs)
external-provisioner | sig-storage-local-static-provisioner | |
---|---|---|
1 | 2 | |
321 | 1,009 | |
1.2% | 1.6% | |
8.6 | 7.6 | |
7 days ago | 12 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
external-provisioner
Posts with mentions or reviews of external-provisioner.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-06-17.
sig-storage-local-static-provisioner
Posts with mentions or reviews of sig-storage-local-static-provisioner.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-11-30.
-
Block and Filesystem side-by-side with K8s and Aerospike
Introduce the Local Static Provisioner
-
K3s Local Path Provisioner Vs K8s sig storage local static provisioner
I'm trying to figuring out the best way to set up the local storage for a K3s cluster, one made up of KVM virtual machines running on one Proxmox VE server. In my research of this matter, I found out that, while K3s comes with its own local path provisioner, there's another local static provisioner available in the K8s sig ecosystem.
What are some alternatives?
When comparing external-provisioner and sig-storage-local-static-provisioner you can also consider the following projects:
local-path-provisioner - Dynamically provisioning persistent local storage with Kubernetes
csi-driver-nfs - This driver allows Kubernetes to access NFS server on Linux node.
container-object-storage-interface-controller - Container Object Storage Interface (COSI) controller responsible to manage lifecycle of COSI objects.
csi-driver-smb - This driver allows Kubernetes to access SMB Server on both Linux and Windows nodes.
csi-driver-image-populator - [EOL] CSI driver that uses a container image as a volume
aerospike-kubernetes-operator - Kubernetes operator for the Aerospike database
external-attacher - Sidecar container that watches Kubernetes VolumeAttachment objects and triggers ControllerPublish/Unpublish against a CSI endpoint
sig-storage-local-static-provisioner vs local-path-provisioner
sig-storage-local-static-provisioner vs csi-driver-nfs
sig-storage-local-static-provisioner vs container-object-storage-interface-controller
sig-storage-local-static-provisioner vs csi-driver-smb
sig-storage-local-static-provisioner vs csi-driver-image-populator
sig-storage-local-static-provisioner vs aerospike-kubernetes-operator
sig-storage-local-static-provisioner vs external-attacher