Important
Although the value of the key inside the ConfigMap has changed, the environment variable in the Pod still shows the earlier value. This is because environment variables for a process running inside a Pod are not updated when the source data changes; if you wanted to force an update, you would need to have Kubernetes replace your existing Pods. The new Pods would then run with the updated information.
Solutions:
- Use
kubectl rollout restart
This will cause the pods to reload with the new environment variables and configuration.
Files:
kubectl rollout restart deployment <deployment-name>
- Use
envFromto Load ConfigMap as Volume
If you want to have more flexibility and allow the pod to pick up updates from the ConfigMap without a restart, you can mount the ConfigMap as a volume.
Files:
