# values.yaml reloader: watchGlobally: false # only watch namespaces with label 'reloader-enabled=true' reloadOnCreate: true # restart pods when a new ConfigMap/Secret is created ignoreSecrets: false ignoreConfigMaps: false If you need a specific fork:
kubectl logs -l app=reloader -n reloader Common log lines: reloader by r1n github
Enter by r1n (commonly found as stakater/Reloader or its derivatives). While the original popular version is maintained by Stakater , the GitHub user r1n has contributed to forks, variants, and discussions that refine this tool. In this comprehensive guide, we’ll explore what Reloader is, its architecture, how to deploy it from GitHub, real-world examples, and why it has become a standard controller for production Kubernetes clusters. What is Reloader? Reloader is a Kubernetes controller that watches for changes in ConfigMap s and Secrets . When it detects an update, it automatically performs a rolling upgrade on any Pods that reference those configuration objects. The result? Your applications pick up the new configuration without downtime, manual kubectl rollout restart , or custom scripts. # values
helm install reloader stakater/reloader --set reloader.watchGlobally=false kubectl label namespace my-app reloader-enabled=true Enable reloadOnCreate to restart pods when a ConfigMap/Secret is created after the workload: What is Reloader
In the dynamic world of Kubernetes, keeping your applications up-to-date with the latest configuration data is a persistent challenge. You can update a ConfigMap or a Secret , but Pods often continue running with the old, cached values, forcing teams into risky manual restarts or complex rolling-update scripts.