WhatBrokeToday
GTA 6FAQ
Kubernetes

Kubernetes Downward API Volumes Ignore Pod-Level CPU and Memory Limits

medium

Is it fixed? Not yet.

Ongoing since Nov 18, 08:47 UTC. First reported Nov 18, 08:47 UTC.

What happened

When PodLevelResources is enabled and container limits are unset while pod-level limits are configured, Downward API volume files for limits.cpu and limits.memory incorrectly report the node's allocatable values instead of the pod limits. Environment variables correctly reflect the pod limits, but file-based reads receive incorrect values, causing applications to misconfigure their heap sizes.

What caused it?

Under active investigation. No report has identified a root cause yet.

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Official fix

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on GitHub issue

    Downward API volumes ignore pod-level CPU and memory limits

    Source

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    Downward API volumes ignore pod-level CPU and memory limits(opens GitHub issue in a new tab)

    What happened? With PodLevelResources enabled, I set CPU and memory limits on a pod and left the container limits unset. The Downward API volume files for limits.cpu and limits.memory reported the node’s allocatable values. Environment variables for the same fields use the pod limits (https://github.com/kubernetes/kubernetes/pull/132605). In my test, the node had 16 GiB of allocatable memory and the pod had a 256 MiB limit. The file reported 16 GiB. An app that reads this file to set its heap…

    by Gandem 0upvotes 3comments

FAQ

What happened in the Kubernetes issue?

When PodLevelResources is enabled and container limits are unset while pod-level limits are configured, Downward API volume files for limits.cpu and limits.memory incorrectly report the node's allocatable values instead of the pod limits. Environment variables correctly reflect the pod limits, but file-based reads receive incorrect values, causing applications to misconfigure their heap sizes.

What is affected by the Kubernetes issue?

Kubernetes.

When did the Kubernetes issue start and end?

It started Nov 18, 08:47 UTC and is still ongoing (19 h 56 min so far). This page updates as it develops.

How do I get alerts for Kubernetes?

Subscribe to the Kubernetes RSS feed for every new Kubernetes incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Kubernetes is down. Kubernetes feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.