The GitHub repository ( github.com/stakater/Reloader ) is actively maintained, well-documented, and ready for production. With a simple Helm install or a single kubectl apply , you can eliminate configuration drift in your cluster permanently. # Install Reloader for free helm repo add stakater https://stakater.github.io/stakater-charts helm install reloader stakater/reloader -n reloader --create-namespace Annotate your deployment kubectl annotate deployment my-app reloader.stakater.com/match=true Watch it work kubectl edit configmap app-config kubectl get pods -w
kubectl apply -f https://raw.githubusercontent.com/stakater/Reloader/master/deployments/kubernetes/reloader.yaml This creates the reloader-reloader deployment, a service account, and the necessary ClusterRole and ClusterRoleBinding. If you want the absolute latest or need to modify the code: reloader by r1n github free
# Add the stakater repo helm repo add stakater https://stakater.github.io/stakater-charts helm repo update Install reloader in a dedicated namespace helm install reloader stakater/reloader --namespace reloader --create-namespace Option 2: Install Manually using Raw YAML If you don’t use Helm, you can apply the raw Kubernetes manifests directly from GitHub. The GitHub repository ( github
annotations: reloader.stakater.com/configmap: "db-config, redis-config, cache-config" reloader.stakater.com/secret: "api-keys, tls-certs" Instead of listing names, you can enable auto-discovery: If you want the absolute latest or need