Graziano Casto

Modern runtimes like Java, Go, and Node.js face a critical "resource gap". They require a massive CPU burst for JIT compilation or dependency loading, only to settle into a much leaner steady state seconds later. Historically, we had to over-provision Pods for this peak, wasting thousands of cores across clusters.

With In-Place Pod Resize in Kubernetes v1.35, we can finally implement a startup boost strategy. This session moves beyond the theory to show the technical "how-to" where we will demonstrate how to build a reactive workflow that provisions high initial resources and then "shrinks" the footprint silently via the resize sub-resource.

Beyond the "how-to", we must address the "shrinkage trap" and explain how to time the resource reclamation to avoid aggressive CPU throttling immediately after boot. We will compare different implementation patterns including sidecar-driven patches, a dedicated boost-operator, and the native Vertical Pod Autoscaler, ensuring your applications don't just start fast but stay stable.

Stop paying for peak startup power during hours of steady-state operation.