Bird
0
0

You notice a Deployment is stuck with fewer pods than desired. Which of these is a likely cause preventing reconciliation?

medium📝 Troubleshoot Q14 of 15
Kubernetes - Fundamentals
You notice a Deployment is stuck with fewer pods than desired. Which of these is a likely cause preventing reconciliation?
AThe kube-apiserver is running normally.
BThe image name in the container spec is correct.
CThe Deployment's selector labels do not match pod labels.
DThe desired replicas count is set to 3.
Step-by-Step Solution
Solution:

  1. Step 1: Check label selectors for matching pods

    If the Deployment's selector labels do not match pod labels, Kubernetes cannot track pods correctly, so reconciliation fails.

  2. Step 2: Understand other options

    Correct image name, running apiserver, and desired replicas do not prevent reconciliation by themselves.

  3. Final Answer:

    The Deployment's selector labels do not match pod labels. -> Option C

  4. Quick Check:

    Label mismatch blocks reconciliation [OK]
Quick Trick: Selector and pod labels must match [OK]
Common Mistakes:
  • Ignoring label selector importance
  • Blaming image name for pod count issues
  • Assuming apiserver status causes pod count

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Kubernetes Fundamentals - Control plane components (API server, scheduler, controller manager, etcd) - Quiz 5medium Labels and Selectors - Using labels for service routing - Quiz 11easy Labels and Selectors - Label selectors (equality, set-based) - Quiz 4medium Namespaces - Default namespaces overview - Quiz 2easy Namespaces - Resource quotas per namespace - Quiz 7medium Pods - Executing commands in Pods - Quiz 8hard Pods - Pod lifecycle states - Quiz 10hard Pods - Executing commands in Pods - Quiz 6medium ReplicaSets and Deployments - Scaling Deployments - Quiz 1easy Services - Headless services concept - Quiz 3easy