Kubernetes DRA Scheduler Fails PreBind with Nil or Empty Request Mappings
Is it fixed? Not yet.
Ongoing since Nov 19, 12:50 UTC. First reported Nov 19, 12:50 UTC.
What happened
Pods referencing a ResourceClaim and requesting an extended resource mapped via extendedResourceName fail PreBind in the DynamicResources plugin with "nil or empty request mappings". This prevents the pod from being bound to nodes where the device plugin provides the extended resource.
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 fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on GitHub issue
DRA scheduler: pod with a ResourceClaim and a device plugin extended resource fails PreBind with "nil or empty request mappings"
Source
Evidence
1 report · 1 GitHubShow
- [1]GitHub First reportDRA scheduler: pod with a ResourceClaim and a device plugin extended resource fails PreBind with "nil or empty request mappings"(opens GitHub issue in a new tab)
What happened? A pod that references a ResourceClaim and also requests an extended resource that a DeviceClass maps through extendedResourceName cannot be bound to a node where a device plugin provides that extended resource. PreBind of the DynamicResources plugin creates an empty <pod>-extended-resources-* ResourceClaim in the API server and then fails with nil or empty request mappings, no update of pod default/my-pod ExtendedResourceClaimStatus. Unreserve deletes the claim, and the next…
by imusmanmalik 0upvotes 1comments
FAQ
What happened in the Kubernetes issue?
Pods referencing a ResourceClaim and requesting an extended resource mapped via extendedResourceName fail PreBind in the DynamicResources plugin with "nil or empty request mappings". This prevents the pod from being bound to nodes where the device plugin provides the extended resource.
What is affected by the Kubernetes issue?
Kubernetes. Also affected at the same time: DigitalOcean.
When did the Kubernetes issue start and end?
It started Nov 19, 12:50 UTC and is still ongoing (20 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.