azure-key-vault-to-kubernetes
secrets-store-csi-driver
azure-key-vault-to-kubernetes | secrets-store-csi-driver | |
---|---|---|
5 | 22 | |
419 | 1,177 | |
0.5% | 1.0% | |
6.7 | 8.5 | |
14 days ago | 4 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.
azure-key-vault-to-kubernetes
-
Need Help Understanding Ingress Controller TLS (AKS)
I used the following stack to generate and sync my certificate : Generation of certs to Keyvault : https://github.com/shibayan/keyvault-acmebot Keyvault cert to AKS sync : https://akv2k8s.io/
-
Best method of setting up TLS on AKS
Can any one either break down how to use the cert I generated in keyvault or suggest another method that's worked for them? I tried using akv2k8s.io which hasn't worked and others have encountered similar problems suggesting they've only got self-signed certs to work.
- Azure AKS/Container App can't access Key vault using managed identity
-
I've been collecting a list of k8s/container tools and sorting them by the number of stars in Github, so far the most complete k8s/container list I know of with almost 250 entries - hoping this is useful for someone else besides me - looking for feedback, ideas for improvement and contributors
Thank you for the kind words. I've added https://github.com/SparebankenVest/azure-key-vault-to-kubernetes to a branch that will be on main soon. Thanks.
-
How to add k8 cluster to access secrets in vault with RBAC
How do I give the cluster permission with RBAC? (GitHub question here: https://github.com/SparebankenVest/azure-key-vault-to-kubernetes/issues/330)
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?
What are some alternatives?
argocd-vault-replacer - An Argo CD plugin to replace placeholders in Kubernetes manifests with secrets stored in Hashicorp Vault.
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
quorum-key-manager - A universal Key & Account Management solution for blockchain applications.
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.
gardener - Kubernetes-native system managing the full lifecycle of conformant Kubernetes clusters as a service on Alicloud, AWS, Azure, GCP, OpenStack, vSphere, KubeVirt, Hetzner, EquinixMetal, MetalStack, and OnMetal with minimal TCO.
external-secrets - External Secrets Operator reads information from a third-party service like AWS Secrets Manager and automatically injects the values as Kubernetes Secrets.
keyvault-acmebot - Automated ACME SSL/TLS certificates issuer for Azure Key Vault (App Service / App Gateway / Front Door / CDN / others)
ingress-nginx - Ingress-NGINX Controller for Kubernetes
awesome-k8s-tools - List of container/k8s tools.
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets