secrets-store-csi-driver-provider-azure
Azure Key Vault provider for Secret Store CSI driver allows you to get secret contents stored in Azure Key Vault instance and use the Secret Store CSI driver interface to mount them into Kubernetes pods. (by Azure)
secrets-store-csi-driver-provider-gcp
Google Secret Manager provider for the Secret Store CSI Driver. (by GoogleCloudPlatform)
| secrets-store-csi-driver-provider-azure | secrets-store-csi-driver-provider-gcp | |
|---|---|---|
| 5 | 6 | |
| 425 | 224 | |
| 0.7% | -0.4% | |
| 7.4 | 7.0 | |
| 2 days ago | 7 days ago | |
| Go | Go | |
| MIT License | 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.
secrets-store-csi-driver-provider-azure
Posts with mentions or reviews of secrets-store-csi-driver-provider-azure.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-14.
- One main source of vulnerabilities in DevOps pipelines is how secrets like keys, certificates, and credentials are managed. Many product engineering teams, for the sake of expediency, hard-code their secrets. This is extremely dangerous.
-
Shhhh... Kubernetes Secrets Are Not Really Secret!
The driver can also sync changes to secrets. The driver currently supports Vault, AWS, Azure, and GCP providers. Secrets Store CSI Driver can also sync provider secrets as Kubernetes secrets; if required, this behavior needs to be explicitly enabled during installation.
-
A better way to manage secrets: reference an external secret defined in the cloud provider environment (please support the idea or give your feedback)
Azure SS-CSI driver
-
Kubernetes with Asp.NET and React and Azure DevOps
Azure Key Vault Provider for Secrets Store CSI Driver allows you to get secret contents stored in an Azure Key Vault instance and use the Secrets Store CSI driver interface to mount them into Kubernetes pods.
-
Service for storing API keys and Kubernetes secrets
Key vault is a good Azure native option. Take look at the secret store CSI driver for Azure https://github.com/Azure/secrets-store-csi-driver-provider-azure
secrets-store-csi-driver-provider-gcp
Posts with mentions or reviews of secrets-store-csi-driver-provider-gcp.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-15.
- Bridging the Gap: Leveraging Secret Store CSI Drivers to Access Secrets from Google Secret Manager in GKE Cluster
-
Shhhh... Kubernetes Secrets Are Not Really Secret!
The driver can also sync changes to secrets. The driver currently supports Vault, AWS, Azure, and GCP providers. Secrets Store CSI Driver can also sync provider secrets as Kubernetes secrets; if required, this behavior needs to be explicitly enabled during installation.
-
A better way to manage secrets: reference an external secret defined in the cloud provider environment (please support the idea or give your feedback)
GCP SS-CSI driver
-
How to Inject Secret From Google Secret Manager into GKE Cluster using Helm Chart?
That's interesting actually, Google provides their own rpvider for the Secrets Store CSI Driver: https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp
-
Has anyone here used Secret Manager before?
Consider: if you have a tool like terraform managing your infra components including your data layer, you likely want to manage those reaources in a different lifecycle from your application code. Applications may also likely managed using a different toolset (kubectl, helm, scaffold, etc.). In this case, secret Manager acts as the secure configuration bridge between the tools, keeping the secrets out of human hands. As certs and passwords are generated on the infra side, those values can be stored as secrets in SM. Application workloads - backed by service accounts having access to read the secret - can decrypt during launch and use the secret as needed. You can use common patterns in both GKE (via thesecrets store csi driver ) and Cloud Run for consuming secrets in this way.
-
How to access secrets in GCP secret manager from PODs
I prefer https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp
What are some alternatives?
When comparing secrets-store-csi-driver-provider-azure and secrets-store-csi-driver-provider-gcp you can also consider the following projects:
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
bank-vaults - A Vault swiss-army knife: A CLI tool to init, unseal and configure Vault (auth methods, secret engines).
Reloader - A Kubernetes controller to watch changes in ConfigMap and Secrets and do rolling upgrades on Pods with their associated Deployment, StatefulSet, DaemonSet and DeploymentConfig – [✩Star] if you're using it!
ingress-nginx - Ingress-NGINX Controller for Kubernetes
csi-gcs - Kubernetes CSI driver for Google Cloud Storage
truenas-csp - TrueNAS Container Storage Provider for HPE CSI Driver for Kubernetes
aws-efs-csi-driver - CSI Driver for Amazon EFS https://aws.amazon.com/efs/
smcache - golang autocert cache implementation for GCP Secret Manager
explore - Community-curated topic and collection pages on GitHub
berglas - A tool for managing secrets on Google Cloud
secrets-store-csi-driver-provider-azure vs vault-secrets-operator
secrets-store-csi-driver-provider-gcp vs secrets-store-csi-driver
secrets-store-csi-driver-provider-azure vs bank-vaults
secrets-store-csi-driver-provider-gcp vs Reloader
secrets-store-csi-driver-provider-azure vs ingress-nginx
secrets-store-csi-driver-provider-gcp vs csi-gcs
secrets-store-csi-driver-provider-azure vs truenas-csp
secrets-store-csi-driver-provider-gcp vs aws-efs-csi-driver
secrets-store-csi-driver-provider-azure vs secrets-store-csi-driver
secrets-store-csi-driver-provider-gcp vs smcache
secrets-store-csi-driver-provider-azure vs explore
secrets-store-csi-driver-provider-gcp vs berglas