Bird
0
0

A Deployment update is stuck and Pods are not updating. What could be a common cause?

medium📝 Troubleshoot Q7 of 15
Kubernetes - ReplicaSets and Deployments
A Deployment update is stuck and Pods are not updating. What could be a common cause?
AReplicas set to zero
BPod template labels changed causing selector mismatch
CDeployment YAML missing apiVersion
DContainer image tag is latest
Step-by-Step Solution
Solution:

  1. Step 1: Understand update mechanism

    Changing Pod template labels breaks selector match, blocking rollout.

  2. Step 2: Check other options

    Replicas zero scales down Pods, missing apiVersion causes apply error, image tag latest is valid.

  3. Final Answer:

    Pod template labels changed causing selector mismatch -> Option B

  4. Quick Check:

    Label mismatch blocks update rollout = B [OK]
Quick Trick: Keep selector and template labels consistent during updates [OK]
Common Mistakes:
  • Changing labels without updating selector
  • Confusing zero replicas with stuck update
  • Ignoring apiVersion errors

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Kubernetes Fundamentals - kubectl CLI installation and configuration - Quiz 2easy Kubernetes Fundamentals - Control plane components (API server, scheduler, controller manager, etcd) - Quiz 14medium Labels and Selectors - Using labels for service routing - Quiz 2easy Labels and Selectors - Adding labels to resources - Quiz 10hard Labels and Selectors - Using labels for service routing - Quiz 13medium Pods - Sidecar container pattern - Quiz 10hard Pods - Pod lifecycle states - Quiz 15hard Services - Service selectors and labels - Quiz 2easy kubectl Essential Commands - kubectl port-forward for local access - Quiz 15hard kubectl Essential Commands - kubectl apply vs create - Quiz 6medium