external-secrets
Reloader
Our great sponsors
external-secrets | Reloader | |
---|---|---|
23 | 34 | |
3,899 | 6,718 | |
5.3% | 4.2% | |
9.7 | 9.0 | |
4 days ago | 1 day 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
Reloader
-
How are people managing env vars for Static Applications?
You can combine this approach with something like https://github.com/stakater/Reloader to automatically restart pods when a certain secret value changes. So if your static code needs to be rebuilt when certain values change, you can use an init container to run the build on startup.
-
Containers are crashing due to memory exhaustion caused by secret rotation every minute.
This is not a cron job? I'm not sure if it helps, but you can have pods do a rolling restart on secret updates: https://github.com/stakater/Reloader that would clear the resources each run, but I'm not entirely clear on what you're looking to achieve.
-
True Secrets Auto Rotation with ESO and Vault
If you use secrets as Environment Variables you will need to use something to make workloads get the new credentials, if they just loose connection. You can use the Reloader project for that.
-
Automating Configuration Updates in Kubernetes with Reloader
Reloader is designed to simplify the process of updating application configurations in Kubernetes. It monitors ConfigMaps and Secrets for changes and triggers rolling upgrades for associated resources such as Deployments, StatefulSets, DaemonSets, and more. Reloader eliminates the need for manual intervention and reduces the risk of errors during the configuration update process.
-
How to start a Go project in 2023
The go k8s packages are pretty bloated - this may also just be a niche case. If you are looking to get secrets with hot reloading, you might also consider mounting a file or setting env vars and coupling it with this reloading operator: https://github.com/stakater/Reloader
-
What Wishlist Features Would You Like To See From K8s?
For the auto restart this has been a staple install in all clusters for years for me: https://github.com/stakater/Reloader
-
Flux & Helm noob here - How do I pass secret values to Helm charts being handled by Flux?
If you didn't want to use SOPS, for some reason, you can certainly take advantage of external secrets as another commenter proposed, but you won't be able to accomplish (2) without an external tool adding to the mix, like Reloader: https://github.com/stakater/Reloader – that's because something has to update the HelmRelease in order to trigger it to upgrade. (You could just wait for the reconciler to come along, but the tendency is to set the polling interval longer than the default, so Helm won't be re-trying as often, in case something goes wrong...)
- Create new pods upon secret/configmap change in pipeline
-
Environment variables - manifest or configMap?
You can install https://github.com/stakater/Reloader And then it's just matter of a single annotation and it restarts automatically when there are changes.
- AWS secret store CSI Driver provider - how to reload pod after SecretProvider update?
What are some alternatives?
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
kubernetes-reflector - Custom Kubernetes controller that can be used to replicate secrets, configmaps and certificates.
vault-secrets-operator - The Vault Secrets Operator (VSO) allows Pods to consume Vault secrets natively from Kubernetes Secrets.
k8s-configmap-watcher
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.
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
trousseau - Store and access your secrets the Kubernetes native way with any external KMS.
helm-charts - Misc helm charts
spiffe-vault - Integrates Spiffe and Vault to have secretless authentication
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.