Architect Using KEDA, Helm, Virtual-Kubelet to Save Cost
summary
Claim: using KEDA with HPA plus Virtual Kubelet and Helm cuts a big ML batch job from ~25 lakh to ~3.5–4 lakh (about 1 lakh was log cost). Setup uses KEDA + HPA to scale by queue depth (RabbitMQ/Kafka scalers), deploys an Azure Function container via a Helm chart scaledObject, and runs pods on Virtual Kubelet on ACI to pay per 0.1 CPU / 0.1 GB RAM. Demo shows queued messages trigger KEDA, HPA creates pods on virtual node, and work completes without full node billing.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:56Agenda and autoscaling
- 5:27Kubernetes HPA limits
- 7:12KEDA scaling solutions
- 9:21Virtual Kubelet cost savings
- 13:32Virtual Kubelet deep dive
- 19:30Helm for Kubernetes
- 20:16KEDA and Virtual Kubelet demo
- 30:26Summary
- 31:31Book promotion
- 34:29Q&A
related talks
48mArchitect using KEDA/Helm/Virtual-Kubelets to save cost
43mKubernetes cost optimisation - How to actually do it
31mScaling Your Cluster (Both Ways)
33mKubernetes cost optimization - How to actually do it
38mScaling EDA Workloads with Kubernetes, KEDA & Karpenter
46mScaling EDA Workloads with Kubernetes, KEDA & Karpenter
37mKubernetes Event-driven Autoscaling with KEDA
35mKEDA - Real Time And Serverless Scaling In Kubernetes
