Q: What is KEDA and how does it extend HPA?
KEDA (Kubernetes Event-Driven Autoscaling) scales pods based on external event sources: Kafka topic lag, RabbitMQ queue depth, HTTP reque...
#Kubernetes #Advanced Scenarios #L3 #Container Orchestration #K8s
🎙️ Candidate Opening & Architectural Context
""Kubernetes is a declarative desired state system; understanding the reconciliation loop is how you diagnose this quickly. 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
KEDA (Kubernetes Event-Driven Autoscaling) scales pods based on external event sources: Kafka topic lag, RabbitMQ queue depth, HTTP request rate, Azure Service Bus, AWS SQS, cron schedules. Standard HPA only uses CPU/memory. KEDA plugs in as a custom metrics source to HPA, enabling scale-to-zero and event-driven scaling. --- *More Kubernetes scenarios added periodically. PRs welcome.* --- ## 🟤 Additional Kubernetes Scenarios (Q101-Q200)
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: KEDA (Kubernetes Event-Driven Autoscaling) scales pods based on external event sources: Kafka topic lag, RabbitMQ queue depth, HTT."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: KEDA (Kubernetes Event-Driven Autoscaling) scales pods based on external event sources: Kafka t
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement