Bird
0
0

Why might a Kubernetes deployment not scale up to the desired number of replicas even after running the scale command?

hard📝 Conceptual Q10 of 15
Kubernetes - ReplicaSets and Deployments
Why might a Kubernetes deployment not scale up to the desired number of replicas even after running the scale command?
Akubectl scale command does not affect deployments
BInsufficient cluster resources to schedule new pods
CThe deployment YAML file is missing
DPods automatically delete after creation
Step-by-Step Solution
Solution:

  1. Step 1: Consider cluster resource limits

    If the cluster lacks CPU or memory, new pods cannot be scheduled.

  2. Step 2: Exclude incorrect reasons

    Deployment YAML exists if deployment runs; kubectl scale does affect deployments; pods do not auto-delete immediately.

  3. Final Answer:

    Insufficient cluster resources to schedule new pods -> Option B

  4. Quick Check:

    Scaling blocked by resource limits [OK]
Quick Trick: Pods need resources; lack blocks scaling [OK]
Common Mistakes:
  • Thinking kubectl scale does nothing
  • Assuming deployment YAML missing stops scaling
  • Believing pods auto-delete after creation

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Kubernetes Fundamentals - Setting up a local cluster (minikube, kind) - Quiz 4medium Labels and Selectors - Label-based filtering with kubectl - Quiz 9hard Namespaces - Limit ranges for defaults - Quiz 3easy Pods - Pod lifecycle states - Quiz 5medium ReplicaSets and Deployments - Desired replicas vs actual replicas - Quiz 9hard ReplicaSets and Deployments - Creating Deployments with YAML - Quiz 10hard ReplicaSets and Deployments - Rollback to previous version - Quiz 9hard Services - Headless services concept - Quiz 7medium Services - ExternalName service type - Quiz 8hard kubectl Essential Commands - kubectl get for listing resources - Quiz 15hard