# Kubernetes v1.36: In-Place Vertical Scaling for Pod-Level Resources Graduates to Beta

DevFeed: [Kubernetes v1.36: In-Place Vertical Scaling for Pod-Level Resources Graduates to Beta](<https://devfeed.tech/articles/kubernetes-v1-36-in-place-vertical-scaling-for-pod-level-resources-graduates-to-beta-4543.md>)

Original publisher: [Read original article](<https://kubernetes.io/blog/2026/04/30/kubernetes-v1-36-inplace-pod-level-resources-beta/>)

Author: Narang Dixita Sohanlal

Published: 2026-04-30T18:35:00Z

Content type: article

Language: en

Sources: [Kubernetes Blog](<https://devfeed.tech/sources/kubernetes-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [autoscaling](<https://devfeed.tech/topics/autoscaling.md>), [Containers](<https://devfeed.tech/topics/containers.md>)

Tags: [containers](<https://devfeed.tech/tags/containers.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [feature](<https://devfeed.tech/tags/feature.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [resources](<https://devfeed.tech/tags/resources.md>), [scale](<https://devfeed.tech/tags/scale.md>), [update](<https://devfeed.tech/tags/update.md>), [v1](<https://devfeed.tech/tags/v1.md>)

## AI overview

Kubernetes v1.36 promotes in-place vertical scaling for pod-level resources to beta and enables it by default. Running Pods can resize their shared aggregate resource budget, often without restarting containers.

## Source excerpt

Following the graduation of Pod-Level Resources to Beta in v1.34 and the General Availability (GA) of In-Place Pod Vertical Scaling in v1.35, the Kubernetes community is thrilled to announce that In-Place Pod-Level Resources Vertical Scaling has graduated to Beta in v1.36! This feature is now enabled by default via the InPlacePodLevelResourcesVerticalScaling feature gate. It allows users to update the aggregate Pod resource budget (.spec.resources) for a running Pod, often without requiring a container restart. Why Pod-level in-place resize? The Pod-level resource model simplified management for complex Pods (such as those with sidecars) by allowing containers to share a collective pool of resources. In v1.36, you can now adjust this aggregate boundary on-the-fly. This is particularly useful for Pods where containers do not have individual limits defined. These containers automatically scale their effective boundaries to fit the newly resized Pod-level dimensions, allowing you to expand the shared pool during peak demand without manual per-container recalculations. Resource inheritance and the resizePolicy When a Pod-level resize is initiated, the Kubelet treats the change as a resize event for every container that inherits its limits from the Pod-level budget. To determine whether a restart is required, the Kubelet consults the resizePolicy defined within individual containers: Non-disruptive Updates: If a container's restartPolicy is set to NotRequired, the Kubelet attempts to update the cgroup limits dynamically via the Container Runtime Interface (CRI). Disruptive Updates: If set to RestartContainer, the container will be restarted to apply the new aggregate boundary safely. Note: Currently, resizePolicy is not supported at the Pod level. The Kubelet always defers to individual container settings to decide if an update can be applied in-place or requires a restart. Example: Scaling a shared resource pool In this scenario, a Pod is defined with a 2 CPU pod-level