Bird
0
0

What happens when you update a ConfigMap in Kubernetes without restarting the pods using it?

easy📝 Conceptual Q11 of 15
Kubernetes - ConfigMaps
What happens when you update a ConfigMap in Kubernetes without restarting the pods using it?
APods continue using the old ConfigMap values until restarted
BPods automatically reload the new ConfigMap values immediately
CKubernetes deletes the pods using the old ConfigMap
DConfigMap update fails if pods are running
Step-by-Step Solution
Solution:

  1. Step 1: Understand ConfigMap behavior on update

    Updating a ConfigMap does not notify or refresh pods automatically.

  2. Step 2: Effect on running pods

    Pods keep using the old ConfigMap data until they are restarted or redeployed.

  3. Final Answer:

    Pods continue using the old ConfigMap values until restarted -> Option A

  4. Quick Check:

    Pods do not auto-refresh ConfigMaps = B [OK]
Quick Trick: Pods need restart to use updated ConfigMaps [OK]
Common Mistakes:
  • Assuming pods auto-refresh ConfigMap changes
  • Thinking ConfigMaps update triggers pod restart automatically
  • Believing ConfigMap updates delete pods

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
ConfigMaps - Creating ConfigMaps from files - Quiz 13medium Health Checks and Probes - TCP probe configuration - Quiz 10hard Ingress - Path-based routing - Quiz 13medium Ingress - Why Ingress manages external access - Quiz 9hard Networking - DNS in Kubernetes (CoreDNS) - Quiz 13medium Resource Management - Why resource management matters - Quiz 7medium Scheduling - Taints and tolerations - Quiz 14medium Scheduling - Node selectors for simple scheduling - Quiz 15hard Secrets - External secret management integration - Quiz 6medium Secrets - External secret management integration - Quiz 14medium