Failing to Autoscale?
summary
Claims that machine learning right-sizes Kubernetes pod CPU/memory requests to stop the cluster autoscaler from adding costly nodes, reporting about 50% reduction in resource requests and an average 8:1 ROI when customers apply recommendations. Implementation consists of a small agent (one container plus a Prometheus scraper) that samples every 15s, retains a year of data but trains on two weeks, emits YAML patch recommendations and an auto-apply with rollback mode, and integrates with HPA/VPA workflows and AWS Carpenter.
AI-written summary · about
chapters (11)
- 0:00Introduction and company background
- 3:32Auto scaling challenges in Kubernetes
- 6:21Over and under provisioning scenarios
- 8:06Market opportunity and waste in cloud costs
- 10:12StormForge solution overview
- 13:02Demo setup and agent installation
- 16:32Recommendation generation and implementation
- 18:21Recap and value proposition
- 21:10Cluster Auto Scaler and AWS partnership
- 22:36Closing and future vision
- 22:56Q&A session
related talks
29mRight-Size Your Kubernetes Deployments
17mScaling Made Simple: Implementing Autoscaling for Optimal K8s Performance
29mKubernetes Autoscaling: Beyond One Size Fits All
22mIntelligent Autoscaling in Enterprise...
14mA Tale of Autoscale: Increasing Resiliency while Reducing On-Call Toil
35mAutoscaling Kubernetes Deployments: A (Mostly) Practical Guide
34mIntroduction to Autoscaling
34mPredictive autoscaling patterns in Kubernetes
