Patrick Ohly 29e92367db DRA device taints: avoid unnecessary Pod lookup ...

When rapidly processing informer events it can happen that a pod gets scheduled
twice (seen only in the TestEviction/update unit test):

- Claim update observed, pod from informer cache with NodeName from update -> queue pod for eviction.
- Pod update observed, claim from informer cache -> queue pod again.

The effect is one additional Get call to the apiserver. We can avoid it by
maintaining an LRU cache with the UIDs of the pods which we have evicted and
thus don't need to do anything for.

2026-02-27 14:38:30 +01:00

..

config

…

metrics

…

device_taint_eviction_test.go

…

device_taint_eviction.go

DRA device taints: avoid unnecessary Pod lookup

2026-02-27 14:38:30 +01:00

doc.go

…

mockqueue_test.go

…

nopqueue.go

…

OWNERS

…

uid_cache.go

DRA device taints: avoid unnecessary Pod lookup

2026-02-27 14:38:30 +01:00