secrets-store-csi-driver-provider-aws
secrets-store-csi-driver-provider-vault
Our great sponsors
| secrets-store-csi-driver-provider-aws | secrets-store-csi-driver-provider-vault | |
|---|---|---|
| 6 | 1 | |
| 422 | 223 | |
| 2.8% | - | |
| 6.9 | 10.0 | |
| 8 days ago | over 1 year 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-provider-aws
- AWS secret store CSI Driver provider - how to reload pod after SecretProvider update?
-
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.
-
Secrets Management on Kubernetes: How do you handle it?
Great suggestions below. If you are a AWS shop and use secrets manager you can use https://github.com/aws/secrets-store-csi-driver-provider-aws
-
A better way to manage secrets: reference an external secret defined in the cloud provider environment (please support the idea or give your feedback)
AWS SS-CSI driver
-
Airflow setup/environment and best practices
For a secrets manager we use the aws secrets store csi driver to fetch our secrets from aws secrets manager and parameter store. On Azure we still need to implement something similar, however an implementation does exist we haven't gotten around to it yet ;)
-
Moving structure to kubernetes, question about secrets and credentials
secrets-store-csi-driver-provider-aws
secrets-store-csi-driver-provider-vault
-
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.
What are some alternatives?
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.
k3d - Little helper to run CNCF's k3s in Docker
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.
secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
helm - The Kubernetes Package Manager
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
kubernetes - Production-Grade Container Scheduling and Management
bank-vaults - A Vault swiss-army knife: A CLI tool to init, unseal and configure Vault (auth methods, secret engines).
Vault - A tool for secrets management, encryption as a service, and privileged access management
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!