Operators update a ConfigMap that is mounted as files into running Pods. Environment variables were also injected from the same ConfigMap at container start. What should an application developer expect?
Select an answer to reveal the explanation.
Short Explanation
Mounted ConfigMap files can refresh like a shared binder someone swapped pages in — eventually. Env vars are snapshots taken when the container started. Either way, many apps still need a nudge to reread config.
Full Explanation
Kubelet periodically refreshes ConfigMap-backed volume contents for running Pods, so mounted files may update after a ConfigMap change, subject to sync timing and cache behavior. Environment variables from ConfigMaps are fixed for the life of the container and change only when Pods are replaced. Applications often must explicitly reload configuration even when files update. ConfigMap edits do not by themselves roll Deployments.