Resize Your Pods w/o Disruptions aka How to Have a Cake and Eat a Cake
summary
Kubernetes is changing pod resizing so resource requests become editable and containers can often grow or shrink without a restart. The proposal adds In-Place Resources Update, new pod fields (desired vs scheduler-allocated vs kubelet-applied), and knobs like resourceRequests mutable, resizePolicy and retryPolicy. Scheduler, kubelet, quota and VPA all get behavior changes; VPA gains in-place only and in-place preferred modes. JVM and other apps needing restart remain supported via the restart option. KEP is pending.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:42Size your workload
- 2:10Everything is changing
- 3:14But why should you care?
- 3:28Contract with the scheduler
- 4:08Scheduling in action
- 8:39VPA updater modes
- 11:23One Simple Trick
- 12:54Fixed-Size Containers
- 13:57Two Scenarios
- 15:05Downscaling Is (NOT) Easy
- 16:41Change Is Coming
- 20:16Flow Control
- 22:42One Little knob
- 25:26Best of the two - eating the cake
- 27:57Feedback
related talks
33mResize Your Pods In-Place With Deterministic eBPF Triggers
36mTaming the Beast: Advanced Resource Management With Kubernetes
29mRight-Size Your Kubernetes Deployments
38mDynamic Pod Resource Boundary Adjustment in Web Scale Clusters
05mResource Roulette: Winning the Kubernetes Allocation Game
38mDynamic Pod Resource Boundary Adjustment in Web Scale Clusters
11mHow Jenga & Tetris Can Help Run More Containers with Lesser Costs...
34mPredictive autoscaling patterns in Kubernetes