Q: What is Vertical Pod Autoscaler (VPA) and when should you use it vs HPA?
VPA adjusts CPU/memory requests of running pods based on actual usage. Use VPA for: workloads where you know they need more resources but...
#Kubernetes #Additional Kubernetes Scenarios (Q101-Q200) #L3 #Container Orchestration #K8s #Terraform State
🎙️ Candidate Opening & Architectural Context
""In our production Kubernetes clusters running microservices on EKS/AKS, this was a classic operational challenge. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Production Solution & Architecture
VPA adjusts CPU/memory requests of running pods based on actual usage. Use VPA for: workloads where you know they need more resources but can't scale horizontally (stateful single replicas). Use HPA for: stateless apps where horizontal scaling makes sense. Don't use both on the same deployment (conflict on CPU metrics).
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: VPA adjusts CPU/memory requests of running pods based on actual usage. Use VPA for: workloads where you know they need more resour."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: VPA adjusts CPU/memory requests of running pods based on actual usage. Use VPA for: workloads w
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement