Kubernetes Event-driven Autoscaling with KEDA
summary
KEDA provides event-driven autoscaling by adding a ScaleObject CRD that creates an HPA per ScaleObject and runs an operator that handles zero→one while HPA handles one→N, so workloads can scale to zero and back. Demo uses RabbitMQ + Helm and a publisher job, hits a configured max 30 replicas and returns to zero successfully. KEDA exposes Prometheus metrics, supports 50+ scalers, triggerAuthentication/cluster credentials (Vault, Azure Key Vault, pod identities), and can spawn ScaleJobs for batch workloads.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:59Agenda
- 2:32Use Case
- 5:41Why Kedah Is Useful
- 9:09Concepts and Architecture
- 14:17Capability of Pausing the Auto Scaling
- 17:18Anti-Authentication
- 18:56Port Identities
- 23:33Triggers
- 23:58Trigger Authentication
- 29:09The Future of the Project
- 30:10Cloud Events
- 35:38Throttling
related talks
35mKEDA - Real Time And Serverless Scaling In Kubernetes
34mAutoscaling Made Easy with Kubernetes Event-Driven Autoscaling (KEDA)
16mEvent Driven Scaler Using Keda
41mEvent-driven autoscaling on Kubernetes with KEDA and Azure Functions
37mKEDA: Unlocking Advanced Event-Driven Scaling for Kubernetes
36mKEDA: Event Driven and Serverless Containers in Kubernetes
50mEvent-driven autoscaling on Kubernetes with KEDA and Azure Functions
31mScaling Your Cluster (Both Ways)
