<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/kubernetes-v1-37-pod-level-resource-managers-graduated-to-beta-fbuyrovry" -->

---
title: Kubernetes v1.37: Pod-Level Resource Managers graduated...
description: Kubernetes v1.37 promotes the Pod-Level Resource Managers feature from Alpha to Beta, though it remains disabled by default. The feature lets Kubelet's...
canonical: https://daily.dev/posts/kubernetes-v1-37-pod-level-resource-managers-graduated-to-beta-fbuyrovry
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Kubernetes v1.37: Pod-Level Resource Managers graduated to Beta | daily.dev
og:description: Kubernetes v1.37 promotes the Pod-Level Resource Managers feature from Alpha to Beta, though it remains disabled by default. The feature lets Kubelet's...
og:url: https://daily.dev/posts/kubernetes-v1-37-pod-level-resource-managers-graduated-to-beta-fbuyrovry
og:image: https://api.daily.dev/og/posts/fbUyroVrY.png
og:image:alt: Kubernetes v1.37: Pod-Level Resource Managers graduated to Beta
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Kubernetes v1.37: Pod-Level Resource Managers graduated to Beta

**[Kubernetes](https://daily.dev/sources/k8s)** · 2 min read · 1 upvotes · 0 comments

## Summary

Kubernetes v1.37 promotes the Pod-Level Resource Managers feature from Alpha to Beta, though it remains disabled by default. The feature lets Kubelet's Topology Manager, CPU Manager, and Memory Manager use pod-level resource declarations directly for hardware placement decisions, enabling hybrid allocation where primary containers get exclusive NUMA-aligned cores while lightweight sidecars share a pod-isolated pool instead of consuming dedicated physical cores. The Beta release also adds top-level cpu_ids and memory fields to the PodResources gRPC API so monitoring tools and device plugins can query pod-level exclusive assignments without double-counting.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://kubernetes.io/blog/2026/09/15/kubernetes-v1-37-pod-level-resource-managers-beta>

## Questions this post answers

### What does the PodLevelResourceManagers feature gate do in Kubernetes 1.37?

It enables the Beta version of Pod-Level Resource Managers, which lets Kubelet's Topology Manager, CPU Manager, and Memory Manager use pod-level resource declarations (.spec.resources) directly for hardware placement decisions. Disabled by default, it allows primary containers to get exclusive NUMA-aligned cores while sidecars share a pod-isolated pool instead of consuming dedicated physical cores. It graduated from Alpha in Kubernetes 1.36.

_Track kubernetes feature-gate changes like this on daily.dev before rolling out cluster upgrades._

### How does Kubernetes handle NUMA alignment for sidecar containers without wasting CPU cores?

With Pod-Level Resource Managers, the Kubelet reserves exclusive NUMA-aligned resources only for primary application containers, while non-Guaranteed sidecars like logging agents or telemetry exporters run in a pod-isolated shared pool. This gives sidecars local NUMA alignment and protection from external node interference without requiring dedicated physical cores for every container in the pod.

_Engineers tuning NUMA-aware Kubernetes workloads follow architecture changes like this on daily.dev._

### What new fields does the PodResources gRPC API expose in Kubernetes 1.37?

The v1 PodResources gRPC service (PodResourcesLister) introduces top-level cpu_ids and memory fields on PodResources responses. This lets monitoring tools and device plugins query pod-level exclusive resource assignments directly without double-counting container-level allocations.

_Teams building Kubernetes monitoring integrations watch API changes like this via daily.dev._

## Similar posts on daily.dev

- [Kubernetes v1.36 Promotes Stability, Compatibility & Reproducibility](https://daily.dev/posts/kubernetes-v1-36-promotes-stability-compatibility-reproducibility-q5x4goaqb) · Cloud Native Now · 14 upvotes · 0 comments
- [Your pod may be requesting 25× more CPU than you think — and Kubernetes won’t tell you](https://daily.dev/posts/your-pod-may-be-requesting-25-more-cpu-than-you-think-and-kubernetes-won-t-tell-you-vixzxfjce) · Dynatrace · 0 upvotes · 0 comments
- [The Efficiency Era: How Kubernetes v1.35 Finally Solves the “Restart” Headache](https://daily.dev/posts/the-efficiency-era-how-kubernetes-v1-35-finally-solves-the-restart-headache-fjhms6zq4) · Cloud Native Now · 22 upvotes · 0 comments

---

Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#orchestration](https://daily.dev/tags/orchestration)

[View this post on daily.dev](https://daily.dev/posts/kubernetes-v1-37-pod-level-resource-managers-graduated-to-beta-fbuyrovry)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Kubernetes v1.37: Pod-Level Resource Managers graduated to Beta","url":"https://daily.dev/posts/kubernetes-v1-37-pod-level-resource-managers-graduated-to-beta-fbuyrovry","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/kubernetes-v1-37-pod-level-resource-managers-graduated-to-beta-fbuyrovry"},"datePublished":"2026-09-16T01:04:10.886Z","dateModified":"2026-09-23T16:14:45.468Z","description":"Kubernetes v1.37 promotes the Pod-Level Resource Managers feature from Alpha to Beta, though it remains disabled by default. The feature lets Kubelet's...","image":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","thumbnailUrl":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","isAccessibleForFree":true,"articleSection":"Kubernetes","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Kubernetes","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/k8s","url":"https://daily.dev/sources/k8s"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/kubernetes-v1-37-pod-level-resource-managers-graduated-to-beta-fbuyrovry","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,orchestration","timeRequired":"PT2M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Kubernetes","item":"https://daily.dev/sources/k8s"},{"@type":"ListItem","position":3,"name":"Kubernetes v1.37: Pod-Level Resource Managers graduated to Beta"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/kubernetes-v1-37-pod-level-resource-managers-graduated-to-beta-fbuyrovry#faq","mainEntity":[{"@type":"Question","name":"What does the PodLevelResourceManagers feature gate do in Kubernetes 1.37?","acceptedAnswer":{"@type":"Answer","text":"It enables the Beta version of Pod-Level Resource Managers, which lets Kubelet's Topology Manager, CPU Manager, and Memory Manager use pod-level resource declarations (.spec.resources) directly for hardware placement decisions. Disabled by default, it allows primary containers to get exclusive NUMA-aligned cores while sidecars share a pod-isolated pool instead of consuming dedicated physical cores. It graduated from Alpha in Kubernetes 1.36. Track kubernetes feature-gate changes like this on daily.dev before rolling out cluster upgrades."}},{"@type":"Question","name":"How does Kubernetes handle NUMA alignment for sidecar containers without wasting CPU cores?","acceptedAnswer":{"@type":"Answer","text":"With Pod-Level Resource Managers, the Kubelet reserves exclusive NUMA-aligned resources only for primary application containers, while non-Guaranteed sidecars like logging agents or telemetry exporters run in a pod-isolated shared pool. This gives sidecars local NUMA alignment and protection from external node interference without requiring dedicated physical cores for every container in the pod. Engineers tuning NUMA-aware Kubernetes workloads follow architecture changes like this on daily.dev."}},{"@type":"Question","name":"What new fields does the PodResources gRPC API expose in Kubernetes 1.37?","acceptedAnswer":{"@type":"Answer","text":"The v1 PodResources gRPC service (PodResourcesLister) introduces top-level cpu_ids and memory fields on PodResources responses. This lets monitoring tools and device plugins query pod-level exclusive resource assignments directly without double-counting container-level allocations. Teams building Kubernetes monitoring integrations watch API changes like this via daily.dev."}}]}
```

