secrets-store-csi-driver
sops
Our great sponsors
secrets-store-csi-driver | sops | |
---|---|---|
22 | 150 | |
1,174 | 15,114 | |
2.1% | 2.4% | |
8.5 | 9.0 | |
2 days ago | about 22 hours ago | |
Go | Go | |
Apache License 2.0 | Mozilla Public 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
-
Check your secrets into Git [video]
I'm not a fan of this approach. I think the Secrets Store CSI Driver (https://secrets-store-csi-driver.sigs.k8s.io/) has a better approach.
-
EKS secrets - Bitnami sealed secrets or KMS?
Secret Store CSI Driver is what we're playing with now. Pretty excellent.
-
How does your company do secret management? AWS/GCP/Azure/Vault/CyberArk etc. thoughts?
If you deploy on k8s, keep your eye on https://secrets-store-csi-driver.sigs.k8s.io/
- K8s secret management
-
Secret Management in Kubernetes: Approaches, Tools, and Best Practices
Considering the major limitations of using Kubernetes Secrets, there are many new approaches being developed by the Kubernetes community. Kubernetes SIGs like the Secrets Store CSI Driver and solutions like the external secrets operator that works with third-party secret managers, and options to seal secrets through tools like bitnami’s sealed-secrets. To skip the tools and move directly to best practices, click here.
-
Azure AKS/Container App can't access Key vault using managed identity
Just to clarify, CSI secret driver is from cncf not Microsoft. Only msft piece is the portion that integrates with key vault. https://secrets-store-csi-driver.sigs.k8s.io/
-
Vault Secrets in K8S, use CRD Injector ?
https://secrets-store-csi-driver.sigs.k8s.io/ and https://developer.hashicorp.com/vault/tutorials/kubernetes/kubernetes-secret-store-driver
-
Shhhh... Kubernetes Secrets Are Not Really Secret!
The Secrets Store CSI Driver is a native upstream Kubernetes driver that can be used to abstract where the secret is stored from the workload. If you want to use a cloud provider's secret manager without exposing the secrets as Kubernetes Secret objects, you can use the CSI Driver to mount secrets as volumes in your pods. This is a great option if you use a cloud provider to host your Kubernetes cluster. The driver supports many cloud providers and can be used with different secret managers.
-
SealedSecrets or external secret operator?
If you want security they are both bad, use something like the secret manager of your choice API directly in your app or https://secrets-store-csi-driver.sigs.k8s.io/ this will keep the actual secrets out of etcd and env vars and give you more security
- Secrets Management on Kubernetes: How do you handle it?
sops
-
Pico.sh – Hacker Labs
My script just sets up default .sops.yaml for https://github.com/getsops/sops
You can further edit .sops.yaml(eg have multiple of them) and decide how you split secrets in your directory tree to further customize who can decrypt the secrets.
It works pretty well for prod/dev splits, etc
-
Encrypting your secrets with Mozilla SOPS using two AWS KMS Keys
Mozilla SOPS (Secrets OPerationS) is an open-source command-line tool for managing and storing secrets. It uses secure encryption methods to encrypt secrets at rest and decrypt them at runtime. SOPS supports a variety of key management systems, including AWS KMS, GCP KMS, Azure Key Vault, and PGP. It's particularly useful in a DevOps context where sensitive data like API keys, passwords, or certificates need to be securely managed and seamlessly integrated into application workflows.
-
An opinionated template for deploying a single k3s cluster with Ansible backed by Flux, SOPS, GitHub Actions, Renovate, Cilium, Cloudflare and more!
Encrypted secrets thanks to SOPS and Age
-
Tracking SQLite Database Changes in Git
We do the exact same thing to keep track of some credentials we use sops[1] and AWS KMS to separate credentials by sensitivity, then use the git differ to view the diffs between the encrypted secrets
Definitely not best practice security-wise, but it works well
[1] https://github.com/getsops/sops
-
The Twelve-Factor App
For anyone new to SOPS like I was - https://github.com/getsops/sops
- Storing and managing private keys
-
Show HN: Shello – Wrangle Environment Variables
I've found this is largely solved by strictly separating plain config and secrets, and then having secrets pull from GCP secret manager / vault / whatever.
You can then commit all the config (including the secret identifiers) and it all just works so long as you're authenticated with your secret storage system.
We do this for the live configuration as well in line with Gitops and find it to work well.
If you don't want to use a cloud secret manager you can also use something like https://github.com/getsops/sops to commit the encrypted secrets safely
-
Check your secrets into Git [video]
Basically, the simpler the better --just encrypt your secrets and check them in to version control.
We use SOPS[0] for this, and have found it to be pretty nice.
[0]: https://github.com/getsops/sops
-
How to secure secrets of docker-compose stacks with git?
The answer is that secrets shouldn't be stored in the git repo at all, but somewhere safe like a password manager or Mozilla's SOPS which people seem to love.
-
Is it safe to commit a Terraform file to GitHub?
Unfortunately, the SOPS project is in some sort of a limbo state and there has been quite a long period with limited maintenance and unclear position from Mozilla. Despite the project being accepted into the CNCF, it's still unclear what will happen with it going forward.
What are some alternatives?
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets
Vault - A tool for secrets management, encryption as a service, and privileged access management
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.
age - A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
external-secrets - External Secrets Operator reads information from a third-party service like AWS Secrets Manager and automatically injects the values as Kubernetes Secrets.
git-crypt - Transparent file encryption in git
ingress-nginx - Ingress-NGINX Controller for Kubernetes
terraform-provider-sops - A Terraform provider for reading Mozilla sops files
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.