Kubernetes v1.37: Pod-Level Resource Managers graduated to Beta
Kubernetes v1.37 graduates the Pod-Level Resource Managers feature to Beta, disabled by default and controlled by the PodLevelResourceManagers feature gate. The Topology Manager, CPU Manager and Memory Manager can now use pod-level resource declarations when making hardware placement decisions. The v1 PodResources gRPC service also adds top-level cpu_ids and memory fields for pod-level exclusive assignments.
What changes for platform teams
Platform teams running latency-sensitive workloads can reserve exclusive NUMA-aligned CPU and memory for primary containers while placing non-Guaranteed sidecars in a pod-isolated shared pool. Teams that opt in should check monitoring and device plugins that read PodResources, since they can now query pod-level assignments without double-counting containers.
Editor: Correction 2026-10-20: this was listed as a Amazon EKS v1.37 release by mistake. It is Kubernetes Blog coverage, not release notes from the project.
Read the original at Kubernetes Blog ↗
written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules