WhatBrokeToday
GTA 6FAQ
Kubernetes

Kubernetes Device Plugin PreStartContainer Fails with Pod-Level Resources

high

Is it fixed? Not yet.

Ongoing since Nov 9, 04:13 UTC. First reported Nov 9, 04:13 UTC.

What happened

Containers requesting a Device Plugin resource fail to start when pod-level CPU and memory resources are specified, PodLevelResources and PodLevelResourceManagers are enabled, and the Topology Manager uses pod scope. Affected containers remain in CreateContainerConfigError with a "no devices found allocated in local cache" error.

What caused it?

The Device Plugin PreStartContainer fails before deferred allocation occurs when using pod-level resources and pod scope in the Topology Manager, because the container's device allocation is not yet present in the local cache.

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

    Device Plugin PreStartContainer fails before deferred allocation with pod-level resources

    Source

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    Device Plugin PreStartContainer fails before deferred allocation with pod-level resources(opens GitHub issue in a new tab)

    What happened? A container requesting a Device Plugin resource cannot start with the following configuration: The Pod specifies pod-level CPU and memory resources. PodLevelResources and PodLevelResourceManagers are enabled. Topology Manager uses pod scope. The Device Plugin advertises PreStartRequired=true. The container's device allocation is not yet present in the local cache. The container remains in CreateContainerConfigError, with an error like: no devices found allocated in local cache…

    by zl86790 0upvotes 3comments

FAQ

What happened in the Kubernetes issue?

Containers requesting a Device Plugin resource fail to start when pod-level CPU and memory resources are specified, PodLevelResources and PodLevelResourceManagers are enabled, and the Topology Manager uses pod scope. Affected containers remain in CreateContainerConfigError with a "no devices found allocated in local cache" error.

What is affected by the Kubernetes issue?

Kubernetes.

When did the Kubernetes issue start and end?

It started Nov 9, 04:13 UTC and is still ongoing (10 d 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.