secrets-store-csi-driver-provider-gcp
berglas
secrets-store-csi-driver-provider-gcp | berglas | |
---|---|---|
6 | 37 | |
224 | 1,224 | |
-0.4% | 0.1% | |
6.8 | 6.9 | |
2 days ago | 24 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.
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
berglas
-
How to deploy a Django app to Google Cloud Run using Terraform
Secret Manager: secure storage for sensitive data e.g passwords.
- How do you handle sensitive variables with a service-worker?
-
Increasing Your Cloud Function Development Velocity Using Dynamically Loading Python Classes
Google Secret Manager
-
Getting started using Google APIs: API Keys (Part 2)
API keys are easy to "leak" or compromise, so best to not only use the restrictions presented to you when you create them but physically protect them as well. Don't code them in plain-text, don't check them into GitHub, etc. Store them in a secure database or use a service like GCP Secret Manager.
-
Need some advice on API key storage
I've been looking at Google Secret Manager which sounds promising but I've not been able to find any examples or tutorials that help with the actual practical details of best practice or getting this working. I'm currently reading about Cloud Functions which also sound promising but again, I'm just going deeper and deeper into GCP without feeling like I'm gaining any useful insights.
-
Secure GitHub Actions by pull_request_target
In this post, I described how to build secure GitHub Actions workflows by pull_request_target event instead of pull_request event. Using pull_request_target, you can prevent malicious codes from being executed in CI. And by managing secrets in secrets management services such as AWS Secrets Manager and Google Secret Manager and access them via OIDC, you can restrict the access to secrets securely. To migrate pull_request to pull_request_target, several modifications are needed. And pull_request_target has a drawback that it's difficult to test changes of workflows, so it's good to introduce pull_request_target to repositories that require strong permissions in CI. For example, a Terraform Monorepo tends to require strong permissions for CI, so it's good to introduce pull_request_target to it.
-
Need Help with Deploying Directus on Google Cloud Platform (GCP)
If you want to make these secrets more secure and get versioning and access logs for them, you may want to switch to Secret Manager later on. They can still be exposed as environment variables to your code. It's a little more setup work, so start with the simple approach at the top.
-
Has anyone been able to implement the OpenAI API with a Firebase Function (which is needed for the env variable API Key)?
https://cloud.google.com/secret-manager https://aws.amazon.com/secrets-manager/
- Securely storing Social Security Numbers with Firebase?
- Dónde van las credenciales cuando voy a subir un código a la nube para correr 24/7?
What are some alternatives?
secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
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!
helm-charts
csi-gcs - Kubernetes CSI driver for Google Cloud Storage
kube-secrets-init - Kubernetes mutating webhook for `secrets-init` injection
aws-efs-csi-driver - CSI Driver for Amazon EFS https://aws.amazon.com/efs/
gitleaks - Protect and discover secrets using Gitleaks 🔑
smcache - golang autocert cache implementation for GCP Secret Manager
cocert - Split and distribute your private keys securely amongst untrusted network
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.
rclone - "rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files