Reloader
gitops-secrets-sample-app
Our great sponsors
Reloader | gitops-secrets-sample-app | |
---|---|---|
34 | 3 | |
6,679 | 18 | |
3.7% | - | |
9.0 | 0.0 | |
6 days ago | about 2 years ago | |
Go | Go | |
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.
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?
gitops-secrets-sample-app
-
What is the best way to set your environment configuration?
Check the whole project here https://github.com/codefresh-contrib/gitops-secrets-sample-app
-
Storing secrets
Vault might be an overkill for your needs. If you are on Kubernetes check out Sealed secrets. See https://github.com/codefresh-contrib/gitops-secrets-sample-app
-
How to Handle Secrets Like a Pro Using Gitops
As a running example, we will use a simple application found at https://github.com/codefresh-contrib/gitops-secrets-sample-app. This is a web application that reads several dummy secrets and displays them (without actually using them in any way).
What are some alternatives?
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.
kubernetes-reflector - Custom Kubernetes controller that can be used to replicate secrets, configmaps and certificates.
kube-secret-syncer - A Kubernetes operator to sync secrets from AWS Secrets Manager
k8s-configmap-watcher
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
helm-charts - Misc helm charts
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.
secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
synator - Synator Kubernetes Secret and ConfigMap synchronizer
external-secrets - External Secrets Operator reads information from a third-party service like AWS Secrets Manager and automatically injects the values as Kubernetes Secrets.
vault-Kubernetes