You manage a deployment with multiple replicas using a ConfigMap mounted as a volume. After updating the ConfigMap, how can you ensure zero downtime while pods receive the updated data?

hard📝 Workflow Q9 of 15

Kubernetes - ConfigMaps

ADelete all pods simultaneously to force recreation with new ConfigMap

BPerform a rolling update of the deployment to restart pods gradually

CManually edit each pod to remount the updated ConfigMap volume

DWait for kubelet to refresh ConfigMap volumes without pod restarts

Step-by-Step Solution

Solution:

Step 1: Understand ConfigMap volume updates
ConfigMap volumes update automatically but some applications may require pod restart to reload config.
Step 2: Use rolling update
Rolling update restarts pods one by one, ensuring continuous availability and updated ConfigMap usage.
Final Answer:
Perform a rolling update of the deployment to restart pods gradually -> Option B
Quick Check:
Rolling updates ensure zero downtime with config changes [OK]

Quick Trick: Use rolling updates to apply ConfigMap changes without downtime [OK]

Common Mistakes:

Deleting all pods causing downtime
Relying on kubelet to refresh config without restart
Editing pods manually instead of deployment

Master "ConfigMaps" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Kubernetes Quizzes

You manage a deployment with multiple replicas using a ConfigMap mounted as a volume. After updating the ConfigMap, how can you ensure zero downtime while pods receive the updated data?

Step 1: Understand ConfigMap volume updates

Step 2: Use rolling update

Final Answer:

Quick Check:

Want More Practice?