Reloader 2.6

Simply update your deployment image tag to stakater/reloader:v2.6.0 and add the desired arguments to the container command.

If any key in my-app-config changed, a rollout happened. reloader 2.6

Managing Custom Resource Definitions (CRDs) during upgrades can be tricky. Often, installation tools (like Helm) try to apply CRDs, while the controller manager inside the cluster tries to manage them too. Often, installation tools (like Helm) try to apply

If you want Reloader to watch everything, you simply add an annotation to your deployment: ://stakater.com: "true" Target Specific Configs How to Use Re-Loader 2

Reloader 2.6 adds the argument --crds-create=false .

The application is portable and does not require installation on the hard drive. How to Use Re-Loader 2.6

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).