hard20 pts · first answer countskuberneteshelmconfigmaps

Config change does not roll Pods

With Helm, you change a value that only affects a ConfigMap. `helm upgrade` succeeds, but the Pods keep running with the old env values. What common chart pattern fixes this?

A.Set the immutable: true field on the ConfigMapB.Put a checksum of the ConfigMap in a Pod annotationC.Add a liveness probe that reads the ConfigMap fileD.Use helm upgrade --force on every single release

Discussion 0

Join free to post in the discussion.

Config change does not roll Pods

Discussion 0

Related questions