A library updates keys in a ConfigMap used as environment variables by catalog Pods. What should ops expect about those running Pods?
Select an answer to reveal the explanation.
Short Explanation
Env vars are stamped when the container starts—like writing settings on a whiteboard at boot. Change the ConfigMap later and those env consumers usually need a fresh Pod; file mounts can catch up after a bit.
Full Explanation
Environment variables populated from a ConfigMap are typically fixed for the life of the container, so Pods often must be restarted (or rolled) to pick up ConfigMap changes. Mounted ConfigMap volumes can update after a delay without a full image rebuild. ConfigMap edits do not rebuild images or change Service ClusterIPs by themselves.