Bird
0
0

A Pod requests 4 CPUs but all nodes in your cluster have only 2 CPUs each. The Pod stays Pending. Which is the best way to fix this?

hard📝 Application Q15 of 15
Kubernetes - Troubleshooting
A Pod requests 4 CPUs but all nodes in your cluster have only 2 CPUs each. The Pod stays Pending. Which is the best way to fix this?
AChange the Pod's image to a smaller size.
BReduce the Pod's CPU request to 2 or less.
CRemove resource requests from the Pod spec.
DAdd a node with at least 4 CPUs to the cluster.
Step-by-Step Solution
Solution:

  1. Step 1: Understand resource requests vs node capacity

    The Pod requests 4 CPUs but nodes have only 2 CPUs, so no node can run it.

  2. Step 2: Choose solution to meet resource needs

    Adding a node with enough CPUs allows the Pod to be scheduled properly.

  3. Final Answer:

    Add a node with at least 4 CPUs to the cluster. -> Option D

  4. Quick Check:

    Pod CPU request > node CPU = add bigger node [OK]
Quick Trick: Match Pod CPU request with node CPU capacity [OK]
Common Mistakes:
  • Reducing CPU request may not be possible or desired
  • Removing requests can cause unstable scheduling
  • Changing image size does not affect CPU requests

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Helm Package Manager - Installing charts - Quiz 6medium Monitoring and Logging - Centralized logging (EFK stack) - Quiz 4medium Operators and Custom Resources - Database operators example - Quiz 4medium Operators and Custom Resources - Operator pattern overview - Quiz 15hard Production Best Practices - Pod Disruption Budgets - Quiz 6medium Production Best Practices - Pod Disruption Budgets - Quiz 2easy Production Best Practices - Multi-cluster management concept - Quiz 9hard RBAC and Security - Why RBAC matters in Kubernetes - Quiz 13medium RBAC and Security - Secrets encryption at rest - Quiz 10hard RBAC and Security - Pod security standards - Quiz 12easy