Automating ConfigMap Reloads: Why We Added Stakater Reloader
· 5 minutes de lecture
Every time I updated the Homer dashboard config, I had to run kubectl rollout restart deployment/homer -n homer after ArgoCD finished syncing. Same for LiteLLM when routing changed. Same for Backstage after any catalog or proxy update. The pattern was identical every time: push to git, wait for ArgoCD sync, then manually trigger a pod restart.
That is an operational smell. If git is the only write path, the restart should be automatic too.