Beyond CAS: Why the world needs another Kubernetes Cluster Autoscaler
summary
Built a IBM Cloud Karpenter provider and benchmarked it against Cluster Autoscaler across EKS and IKS using Terraform, Ansible, kube-burner, Prometheus and cloud billing APIs; experiments run four clusters (3 initial nodes, max 10), 1‑hour tests with a 20‑minute spike. Implementation faces IBM API sprawl and custom CRD work. Results show 33% fewer nodes on average, about 50% faster provisioning latency, and cost savings up to 33% on AWS and ~20–23% on IKS.
AI-written summary · about
chapters (11)
- 0:00Research project intro
- 1:06Why autoscaling matters
- 4:01How Cluster Autoscaler works
- 6:52Introducing Carpenter
- 9:44Carpenter on IBM Cloud
- 11:31Benchmarking setup
- 13:59Automation with Ansible
- 15:50Workload simulation with Kube-burner
- 17:14Results and savings
- 18:40Does the world need it?
- 19:45Q&A
related talks
39mCluster API & Cluster Autoscaler
21mWhy should you bother about cluster autoscaling- Karpenter
27mHarness the power of Karpenter to scale, optimize & upgrade K8s
22mKarpenter Efficient scaling of Kubernetes clusters
45mYour K8s Infinity Gaunlet: The Marvel of KEDA and Cluster-API for Infinite Scale
27mScaling K8s Clusters Without Losing Your Mind or Money
32mRun Cluster Autoscaler on Your Own Cloud; or, Why Do We Need Cluster API?
22mUse Karpenter to scale, optimize & upgrade K8s
