Bird
0
0

A Deployment shows desired replicas as 4 but actual replicas is 0. What is the most likely cause?

medium📝 Troubleshoot Q7 of 15
Kubernetes - ReplicaSets and Deployments
A Deployment shows desired replicas as 4 but actual replicas is 0. What is the most likely cause?
APods are stuck in Pending due to resource limits
BDeployment is paused and not creating Pods
CPods are running but not counted correctly
DDeployment YAML has syntax errors
Step-by-Step Solution
Solution:

  1. Step 1: Understand zero actual replicas

    Desired is 4 but no Pods running means Pods are not starting.

  2. Step 2: Identify common cause

    Pods stuck in Pending often happen due to insufficient resources or scheduling issues.

  3. Final Answer:

    Pods are stuck in Pending due to resource limits -> Option A

  4. Quick Check:

    Pending Pods cause actual replicas to be zero [OK]
Quick Trick: Pending Pods mean actual replicas stay at zero [OK]
Common Mistakes:
  • Assuming Deployment is paused without checking
  • Thinking Pods run but not counted
  • Blaming YAML syntax without error messages

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Labels and Selectors - Why labels organize resources - Quiz 6medium Labels and Selectors - Label selectors (equality, set-based) - Quiz 3easy Pods - Init containers - Quiz 6medium ReplicaSets and Deployments - ReplicaSet definition - Quiz 2easy ReplicaSets and Deployments - Recreate update strategy - Quiz 9hard ReplicaSets and Deployments - Creating Deployments with YAML - Quiz 10hard Services - Service selectors and labels - Quiz 10hard Services - Headless services concept - Quiz 6medium kubectl Essential Commands - kubectl explain for API reference - Quiz 2easy kubectl Essential Commands - kubectl exec for container access - Quiz 3easy