Back to news
security Priority 5/5 5/2/2026, 11:05:47 AM

Kubernetes v1.36 Graduates In-Place Pod-Level Resource Vertical Scaling to Beta

Kubernetes v1.36 Graduates In-Place Pod-Level Resource Vertical Scaling to Beta

The Kubernetes community has announced that In-Place Pod-Level Resources Vertical Scaling has officially graduated to Beta in version v1.36. This feature builds upon the previous Pod-Level Resources graduation in v1.34 and the general availability of In-Place Pod Vertical Scaling in v1.35. It represents a significant step forward in fine-tuning resource management for complex workloads that require dynamic adjustments without the overhead of container restarts. This update allows for more granular control over resource allocation by shifting the focus from individual containers to the entire Pod structure. Administrators can now modify CPU and memory settings dynamically, which is particularly beneficial for applications with fluctuating resource demands. The implementation ensures that the Pod stays running while the underlying node resources are adjusted to match the new specifications. Security and stability remain a priority with this update, as the release includes specific prerequisites for staged rollouts. Operational teams should review the impact on existing environments, particularly concerning scheduling and node-level resource accounting. Proper configuration of the container runtime is required to ensure that the resizing signals are correctly interpreted and applied without disrupting service availability.

Related tools

Recommended tools for this topic

These picks prioritize high-intent tools relevant to this topic. Some links may include partner or affiliate tracking.

#kubernetes#devops#cloud#official

Comparison

AspectBefore / AlternativeAfter / This
Resize TriggerRequires Pod restart or replacementUpdate Spec in-place without restart
Resource ScopeContainer-level resource definitionPod-level aggregate resource definition
AvailabilityPotential downtime during pod rolloutZero-downtime resource adjustments
API MaturityAlpha / ExperimentalBeta (enabled by default)

Action Checklist

  1. Verify Kubernetes control plane version Ensure the cluster is upgraded to at least v1.36 to access Beta features
  2. Review Container Runtime compatibility Confirm your CRI supports in-place resizing signals
  3. Update Pod specifications to use pod-level resources Transition from container-specific limits to pod-level requests where applicable
  4. Test resizing under load Validate that applications handle memory or CPU changes without instability
  5. Monitor node resource accounting Ensure metrics-server or other monitoring tools reflect the in-place changes correctly

Source: Kubernetes Blog

This page summarizes the original source. Check the source for full details.

Related