KEP-5055keps/sig-scheduling/5055-dra-device-taints-and-tolerations
DRA: device taints and tolerations
With Dynamic Resource Allocation (DRA), DRA drivers publish information about the devices that they manage in ResourceSlices. This information is used by the scheduler when selecting devices for user requests in ResourceClaims. With this KEP, DRA drivers can mark devices as tainted such that they won't be used for scheduling new pods. In addition, pods alre… Full summary
With Dynamic Resource Allocation (DRA), DRA drivers publish information about the devices that they manage in ResourceSlices. This information is used by the scheduler when selecting devices for user requests in ResourceClaims. With this KEP, DRA drivers can mark devices as tainted such that they won't be used for scheduling new pods. In addition, pods already running with access to a tainted device can be stopped automatically. Cluster administrators can do the same by creating a DeviceTaintRule which applies a taint to all devices matching certain selection criteria, like all devices of a certain driver. Users can decide to ignore specific taints by adding tolerations to their ResourceClaim.
Facts
- Authors
- @pohly@everpeace
- Approvers
- @macsko
- Tracking issue
- #5055(opens GitHub in a new tab) closedcompletedclosed 2026-09-11 10:19 UTCmilestone v1.37sig/nodesig/schedulingstage/stablewg/device-management
- Milestones
- alpha v1.33beta v1.36stable v1.37
- Participating SIGs
- none
- Feature gates
- DRADeviceTaintRules, DRADeviceTaints
- Created / last updated
- 2025-01-20 / none