You change a value in your Helm chart. helm upgrade succeeds. The ConfigMap in the cluster shows the new value. And your app keeps behaving exactly as before.
Nothing failed β that's the problem. Kubernetes did precisely what it was told.
Why it happens
A Deployment only rolls its pods when the pod template changes. A ConfigMap is a separate object. When you update it, the pods already running don't notice:
Values injected as environment variables are read once, at container start. They stay old until the pod restarts.
Values mounted as files do update eventually, but only if your app re-reads the file. Most apps read config once at boot.
So the upgrade "worked", the config is "deployed", and production runs the old settings until something else happens to restart the pods β a node drain, a crash, the next image release.β¦