DRA: Device Taints: tolerating NoExecute is broken #134434
Description
What happened?
When a ResourceClaim is affected by a NoExecute taint and has a toleration for that taint, then the scheduler schedules a Pod using that ResourceClaim correctly. But it does not copy the toleration into the allocation result and then the eviction controller evicts the Pod more or less instantaneously before it even starts to run.
What did you expect to happen?
Pod should run.
How can we reproduce it (as minimally and precisely as possible)?
See description.
Anything else we need to know?
No response
Kubernetes version
Kubernetes >= 1.33 where the feature was introduced.
Cloud provider
OS version
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here