Kubernetes ยท Immutable ConfigMaps

What happens when someone edits a ConfigMap?

The lock is checked first. If the data is not locked, what a running Pod sees depends on how it receives the setting.

What happens when someone edits a ConfigMap Flowchart: an edit to an immutable ConfigMap is rejected; an edit to a mutable one is saved, then environment variables and subPath files keep old values until the Pod is replaced, while normal volume files update after a delay. YES NO ENV VARIABLE VOLUME FILE SUBPATH FILE Someone edits the data kubectl edit / apply Is the data locked? immutable: true Edit is rejected field is immutable running Pods unaffected New data is saved ConfigMap is updated How does the Pod get the setting? Keeps the old value until the Pod is replaced File updates later after a short delay; app may need a reload Keeps the old file until the Pod is replaced LEGEND Start or outcome Step Decision Path the lock protects