You have a deployment using a ConfigMap for environment variables. After updating the ConfigMap, you want all pods to use the new values without downtime. What is the best approach?

hard📝 Workflow Q15 of 15

Kubernetes - ConfigMaps

AUpdate the ConfigMap and wait; pods auto-refresh environment variables

BDelete all pods manually to force recreation with new ConfigMap

CUpdate the ConfigMap and run <code>kubectl rollout restart deployment/myapp</code>

DEdit each pod to mount the new ConfigMap version

Step-by-Step Solution

Solution:

Step 1: Understand environment variable update behavior
Pods do not auto-refresh environment variables from ConfigMap updates.
Step 2: Use rollout restart for zero downtime update
Rolling restart updates pods one by one, applying new ConfigMap values without downtime.
Final Answer:
Update the ConfigMap and run kubectl rollout restart deployment/myapp -> Option C
Quick Check:
Rollout restart updates pods gracefully = A [OK]

Quick Trick: Use rollout restart for zero downtime ConfigMap update [OK]

Common Mistakes:

Expecting pods to auto-refresh env vars
Deleting pods causing downtime
Editing pods directly which is not recommended

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 have a deployment using a ConfigMap for environment variables. After updating the ConfigMap, you want all pods to use the new values without downtime. What is the best approach?

Step 1: Understand environment variable update behavior

Step 2: Use rollout restart for zero downtime update

Final Answer:

Quick Check:

Want More Practice?