: It runs as a tiny pod in your cluster. Zero Manual Intervention : No more kubectl rollout restart .
In previous versions, if you annotated a resource to watch a ConfigMap, Reloader would trigger an update whenever any change occurred in that ConfigMap. But what if you have a ConfigMap that contains multiple keys, and your application only cares about one of them? reloader 2.6
: Works for sensitive data just as easily as config files. 🚀 How It Works : It runs as a tiny pod in your cluster
Managing configuration in Kubernetes can be a headache. When you update a or a Secret , the pods consuming them don't always realize things have changed. Traditionally, this meant manual restarts or complex custom scripts. But what if you have a ConfigMap that
With , you can now tell Reloader to only trigger an update if the specific keys referenced in your annotation actually change.
If you only want a restart when a specific file changes, you can name it directly: ://stakater.com: "my-configmap" 🛠️ Getting Started in 3 Steps : helm install reloader stakater/reloader
Reloader 2.6 introduces an --is-openshift flag. While Reloader has generally worked on OpenShift, this flag ensures that the operator logic optimizes specifically for OpenShift security contexts and resource discovery. This provides a smoother "out-of-the-box" experience for OpenShift users without requiring manual tweaks to RoleBased Access Controls (RBAC).
