Reloader
k8s-configmap-watcher
DISCONTINUED
Our great sponsors
Reloader | k8s-configmap-watcher | |
---|---|---|
34 | 1 | |
6,590 | 11 | |
4.6% | - | |
9.0 | 10.0 | |
1 day ago | 10 months ago | |
Go | Go | |
Apache License 2.0 | MIT License |
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 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
- AWS secret store CSI Driver provider - how to reload pod after SecretProvider update?
-
State of Kubernetes Secrets Management in 2022
Unfortunately, there isn't one out-of-the-box, elegant solution for triggering deployments to be reloaded with the solutions we've shown. You'd need to rely on open source tools such as Reloader, which watches for changes in ConfigMap and Secrets and does rolling upgrades on Pods with their associated Deployment, StatefulSet, DaemonSet, and DeploymentConfig.
-
One multi-container deployment vs. a separate deployment for each image?
It makes sense to use multiple containers for the same deployment, if they serve the same purpose, i.e. if there's a reloader present etc.
- Kubernetes Reload/Restart pod on file changes
-
How to monitor secret changes in Kubernetes?
If you just need to restart pods, https://github.com/stakater/Reloader might be a good option. Anything more advanced will likely require a component that integrates with the Kube API.
-
How should I manage my Helm charts?
E.g. on a cloud provider use their secrets management solution. Bring the secrets from git/sops into their store, then for the application use external-secrets to bring a copy into your namespace and update your deployments with reloader.
-
Sharing/syncing secrets across clusters
on top of that combine https://github.com/stakater/Reloader into the mix to bounce pods around when it detects a cm or secret that gets updated from upstream
- Trigger redeployment after configmap change?
k8s-configmap-watcher
What are some alternatives?
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
kubernetes-reflector - Custom Kubernetes controller that can be used to replicate secrets, configmaps and certificates.
helm-charts - Misc helm charts
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
secrets-store-csi-driver-provider-gcp - Google Secret Manager provider for the Secret Store CSI Driver.
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
crc - CRC is a tool to help you run containers. It manages a local OpenShift 4.x cluster, Microshift or a Podman VM optimized for testing and development purposes
paste-secret - Paste your GitHub Secrets to files
Watch - Watches for changes in a directory tree and reruns a command in an acme win or just on the terminal.