smcache
secrets-store-csi-driver-provider-gcp
| smcache | secrets-store-csi-driver-provider-gcp | |
|---|---|---|
| 1 | 6 | |
| 8 | 224 | |
| - | -0.4% | |
| 2.8 | 6.8 | |
| 6 months ago | 3 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.
smcache
secrets-store-csi-driver-provider-gcp
- 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?
roxy - Roxy the Frontend Proxy
secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
squealer - Telling tales on you for leaking secrets!
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!
polyapp
csi-gcs - Kubernetes CSI driver for Google Cloud Storage
aws-efs-csi-driver - CSI Driver for Amazon EFS https://aws.amazon.com/efs/
berglas - A tool for managing secrets on Google Cloud
secrets-store-csi-driver-provider-aws - The AWS provider for the Secrets Store CSI Driver allows you to fetch secrets from AWS Secrets Manager and AWS Systems Manager Parameter Store, and mount them into Kubernetes pods.
k3d - Little helper to run CNCF's k3s in Docker
external-secrets - External Secrets Operator reads information from a third-party service like AWS Secrets Manager and automatically injects the values as Kubernetes Secrets.
secrets-store-csi-driver-provider-vault - HashiCorp Vault Provider for Secret Store CSI Driver [Moved to: https://github.com/hashicorp/vault-csi-provider]