Why does updating a ConfigMap sometimes not affect a running Pod at all?

If the ConfigMap was consumed as an environment variable, that value was injected once at container start and stays frozen until the Pod restarts — only volume-mounted ConfigMaps update their files live (via kubelet's periodic sync), without a restart.