Microservices - Orchestration with Kubernetes
You want to design a microservices system that scales pods horizontally based on both CPU usage and custom queue length metrics. Which approach best uses Horizontal Pod Autoscaler to achieve this?
You want to design a microservices system that scales pods horizontally based on both CPU usage and custom queue length metrics. Which approach best uses Horizontal Pod Autoscaler to achieve this?
hard📝 Trade-off Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Understand HPA multi-metric support
Horizontal Pod Autoscaler supports multiple metrics in a single configuration to scale pods based on combined criteria.Step 2: Evaluate options for best practice
Configure HPA with multiple metrics: CPU utilization and custom queue length, setting thresholds for both uses multiple metrics in one HPA, which is efficient and avoids conflicts from multiple HPAs targeting the same deployment.Final Answer:
Configure HPA with multiple metrics: CPU utilization and custom queue length, setting thresholds for both -> Option AQuick Check:
Single HPA with multiple metrics = A [OK]
Quick Trick: Use one HPA with multiple metrics for combined scaling [OK]
Common Mistakes:
MISTAKES- Using multiple HPAs on same deployment causing conflicts
- Ignoring custom metrics support
- Relying only on CPU metrics
Master "Orchestration with Kubernetes" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes