external-secrets
trousseau
| external-secrets | trousseau | |
|---|---|---|
| 23 | 1 | |
| 4,514 | 176 | |
| 2.5% | 0.0% | |
| 9.8 | 1.4 | |
| 2 days ago | about 1 year 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.
external-secrets
- GKE Backup to only backup secrets?
- How to securely store configs across microservices and not commit secrets to vc
-
On AWS: Why use EKS instead of ECS?
Something I personally like about EKS is the Amazon Controllers for Kubernetes nowadays they would more preoperly be called 'operators' like the (non AWS and non AWS specific) External Secrets Operator. Essentially you delegate your cluster to create external resources elsewhere on your behalf based on annotations in your deployment.
- How do you rotate 3rd parties API keys?
-
Self-hosted Secrets Manager (or something alike)
Vault is extremely complex and heavy for my tastes, and Bitwarden Secrets Manager implementation AFAIU is not open source and not suitable for self-hosting. I like that both can be easily integrated with External Secrets for kubernetes secrets management.
-
How to Deploy and Scale Strapi on a Kubernetes Cluster 1/2
Store the Secrets in a vault like Hashicorp Vault, AWS Secrets Manager, GCP Secret Manager, etc., and then use an operator like External Secrets Operator to add them to your K8s cluster.
-
GitOps and Kubernetes – Secure Handling of Secrets
External Secrets is an operator that integrates external KMS such as Hashicorp Vault or those of the major cloud providers. It reads secrets from the external APIs and injects them into Kubernetes secrets. The operator is a new implementation after the merge of similar projects from GoDaddy and ContainerSolutions.
- Accessing ENV variables from cronjob
- How do I manage my Kubernetes secrets?
-
How do I manage Kubernetes Secrets?
I use Kubernetes-External-Secrets https://github.com/external-secrets/external-secrets with aws parameter store
trousseau
-
Are you using Vault?
I usually use trousseau, the secrets are still in k8s but they are encrypted with a key that is in Vault. It is utilising Kubernetes KMS keys, so the decryption and encryption is happening automatically as long as the correct RBAC is applied.
What are some alternatives?
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
medusa - A cli tool for importing and exporting Hashicorp Vault secrets
secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
teller - Cloud native secrets management for developers - never leave your command line for secrets.
vault-secrets-operator - The Vault Secrets Operator (VSO) allows Pods to consume Vault secrets natively from Kubernetes Secrets.
spiffe-vault - Integrates Spiffe and Vault to have secretless authentication
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-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
vault-plugin-secrets-qdrant - A Vault plugin for the Qdrant vector database
ktunnel - A cli that exposes your local resources to kubernetes
kube-score - Kubernetes object analysis with recommendations for improved reliability and security. kube-score actively prevents downtime and bugs in your Kubernetes YAML and Charts. Static code analysis for Kubernetes.