Kubernetes - ReplicaSets and Deployments
You notice your Deployment's desired replicas is 5 but actual replicas stays at 3. Which is the most likely cause?
You notice your Deployment's desired replicas is 5 but actual replicas stays at 3. Which is the most likely cause?
medium📝 Troubleshoot Q14 of 15
Step-by-Step Solution
Solution:
Step 1: Understand why actual replicas lag behind desired
If actual replicas are less than desired, pods may be stuck starting, often due to resource constraints.Step 2: Eliminate other options
Syntax errors prevent deployment creation, incorrect kubectl commands won't show this state, and actual replicas do not update instantly.Final Answer:
Pods are stuck in Pending state due to resource limits -> Option AQuick Check:
Pending pods cause actual < desired replicas [OK]
Quick Trick: Check pod status if actual replicas < desired replicas [OK]
Common Mistakes:
- Assuming syntax errors cause replica mismatch
- Expecting instant replica count update
- Ignoring pod scheduling issues
Master "ReplicaSets and Deployments" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes