Post

Kubernetes v1.37 can preempt lower-priority workloads to make room for higher-priority in-place Pod resize requests. A useful scheduling principle: Elasticity isn’t only adding capacity. It’s deciding who gets the capacity already available. kubernetes.io/blog/2026/09... #Kubernetes #CloudNative

kubernetes.ioKubernetes v1.37: Scheduler Preemption for In-Place Pod Resize (Alpha)In Kubernetes, resource allocation has historically been a static decision made during a Pod's initial scheduling and placement. With the graduation of the core in-Place Pod resize feature to General ...

12/10/26, 9:17 pm0 reposts1 like

YAMLwrangler

@jmm86.bsky.social

Elasticity lies in optimizing existing resources, not just adding more. What other scenarios leverage this principle effectively?

Ioannis Polyzos

@ipolyzos.com

A few examples come to mind: workload preemption, VPA for right-sizing resource requests, and DRA for sharing scarce hardware like GPUs. For me the interesting part is how Kubernetes is moving beyond resource allocation being a scheduling decision, towards adapting to changing workload needs

The Projekt

@wearetheprojekt.bsky.social

The fun failure mode is a resize that evicts a pod which then fits nowhere else, so one memory bump costs you a replica. PodDisruptionBudgets start mattering for resizes too.

Ioannis Polyzos

@ipolyzos.com

great point. A successful resize shouldn’t come at the cost of overall workload availability. Preemption needs to account for placement feasibility and disruption budgets, not just priority.