Updating ConfigMaps and propagation in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a ConfigMap in Kubernetes?

A ConfigMap is a Kubernetes object used to store non-confidential configuration data in key-value pairs. It allows you to separate configuration from container images to keep containers portable.

beginner

How do you update a ConfigMap in Kubernetes?

You can update a ConfigMap by editing it with 'kubectl edit configmap <name>' or by applying a new YAML file with 'kubectl apply -f '.

intermediate

Does updating a ConfigMap automatically update the pods using it?

No, updating a ConfigMap does not automatically update pods. Pods must be restarted or recreated to pick up the new ConfigMap values.

intermediate

What is a common method to propagate ConfigMap changes to running pods?

A common method is to delete pods so that the Deployment or ReplicaSet recreates them with the updated ConfigMap, or to trigger a rolling update by changing pod template annotations.

advanced

Can ConfigMap changes be automatically reflected inside a running container without restart?

ConfigMap changes mounted as files in volumes can be updated inside running containers, but applications must watch and reload the config. Environment variable changes require pod restart.

Which command updates a ConfigMap from a YAML file?

A kubectl apply -f configmap.yaml

B kubectl run configmap.yaml

C kubectl create pod configmap.yaml

D kubectl delete configmap.yaml

Use 'kubectl apply -f' to update or create resources from a YAML file.

After updating a ConfigMap, what must you do to apply changes to pods using it?

A Nothing, pods update automatically

B Restart or recreate the pods

C Run 'kubectl update pods'

D Delete the ConfigMap

Pods do not automatically reload ConfigMap changes; they must be restarted or recreated.

How can you trigger a rolling update to propagate ConfigMap changes?

A Edit the ConfigMap directly inside the pod

B Delete the ConfigMap

C Run 'kubectl scale deployment'

D Change pod template annotations

Changing pod template annotations forces a rolling update, recreating pods with new config.

Which ConfigMap mounting method allows live updates inside running containers?

A Passed as environment variables

B Embedded in container image

C Mounted as files in volumes

D Stored in pod annotations

ConfigMaps mounted as files can be updated live; environment variables require pod restart.

What happens if you update a ConfigMap but do not restart pods using it?

A Pods continue using old config

B Pods automatically reload new config

C Pods crash immediately

D Pods delete themselves

Pods keep using the old ConfigMap data until restarted or recreated.

Explain how ConfigMap updates propagate to running pods in Kubernetes.

Think about pod lifecycle and how config is loaded.

Describe the difference between ConfigMap data mounted as environment variables versus as files regarding updates.

Consider how containers read environment variables vs files.