Kubernetes - Resource Management
You have configured an HPA for a deployment, but it is not scaling pods despite high CPU usage. Which of the following is a likely cause?
You have configured an HPA for a deployment, but it is not scaling pods despite high CPU usage. Which of the following is a likely cause?
medium📝 Troubleshoot Q6 of 15
Step-by-Step Solution
Solution:
Step 1: Understand HPA metric dependency
HPA relies on metrics-server to collect CPU and memory metrics.Step 2: Identify common causes for no scaling
If metrics-server is missing or malfunctioning, HPA cannot get metrics and won't scale.Step 3: Evaluate other options
The deployment has more than 10 replicas already is irrelevant; HPA can scale up to maxReplicas. The HPA minReplicas is set higher than maxReplicas is invalid config but would cause errors. The deployment is using a StatefulSet instead of Deployment is incorrect as HPA can target StatefulSets too.Final Answer:
The metrics-server is not installed or not functioning properly -> Option DQuick Check:
Metrics-server availability is critical for HPA [OK]
Quick Trick: HPA needs metrics-server to fetch metrics for scaling [OK]
Common Mistakes:
- Assuming HPA works without metrics-server
- Confusing deployment type with scaling capability
- Ignoring configuration errors in min/max replicas
Master "Resource Management" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes