azurefile-csi-driver
vault-csi-provider
| azurefile-csi-driver | vault-csi-provider | |
|---|---|---|
| 4 | 1 | |
| 147 | 291 | |
| 2.0% | 0.3% | |
| 0.0 | 7.9 | |
| 1 day ago | 13 days ago | |
| Go | Go | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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.
azurefile-csi-driver
-
Introduction to Day 2 Kubernetes
Any Kubernetes cluster requires persistent storage - whether organizations choose to begin with an on-premise Kubernetes cluster and migrate to the public cloud, or provision a Kubernetes cluster using a managed service in the cloud. Kubernetes supports multiple types of persistent storage – from object storage (such as Azure Blob storage or Google Cloud Storage), block storage (such as Amazon EBS, Azure Disk, or Google Persistent Disk), or file sharing storage (such as Amazon EFS, Azure Files or Google Cloud Filestore). The fact that each cloud provider has its implementation of persistent storage adds to the complexity of storage management, not to mention a scenario where an organization is provisioning Kubernetes clusters over several cloud providers. To succeed in managing Kubernetes clusters over a long period, knowing which storage type to use for each scenario, requires storage expertise.
- Is it possible connection Kubernetes on-premise with Azure File Storage?
- Azure Kubernetes Service — Next level persistent storage with Azure Disk CSI driver
-
k8s cluster on premise claim disk on azure
Azure Disk CSI is only usable within Azure since it mounts the disk directly to the VM. You can’t mount it to your on-premise Kubernetes node. If using Azure storage is a requirement, you can look into Azure File CSI driver (https://github.com/kubernetes-sigs/azurefile-csi-driver), which will let you mount Azure storage folders as PVs in your on-prem cluster.
vault-csi-provider
-
Inject Secrets into your Pod Environments at the Container Runtime
Why not use https://github.com/kubernetes-sigs/secrets-store-csi-driver to do this? Then you don't have a strict binding to runc. A live example of using the CSI driver with a secrets provider is https://github.com/hashicorp/vault-csi-provider
What are some alternatives?
azuredisk-csi-driver - Azure Disk CSI Driver
bank-vaults - A Vault swiss-army knife: A CLI tool to init, unseal and configure Vault (auth methods, secret engines).
aws-ebs-csi-driver - CSI driver for Amazon EBS https://aws.amazon.com/ebs/
aws-efs-csi-driver - CSI Driver for Amazon EFS https://aws.amazon.com/efs/
csi-gcs - Kubernetes CSI driver for Google Cloud Storage
secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
gcp-compute-persistent-disk-csi-driver - The Google Compute Engine Persistent Disk (GCE PD) Container Storage Interface (CSI) Storage Plugin.
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
aws-efs-csi-driver - CSI Driver for Amazon EFS https://aws.amazon.com/efs/ [Moved to: https://github.com/kubernetes-sigs/aws-efs-csi-driver]
topolvm - Capacity-aware CSI plugin for Kubernetes
vault-creds - Sidecar container for requesting dynamic Vault database secrets