Patrick Ohly 09a3e27741 DRA consumable capacity: fix allocation result lookup ...

Two in-tree places looked for entries with a literal string lookup.  This
compared a QualifiedName from a current slice against a QualifiedName from an
allocation result, which is based on some older slice. The literal lookup
breaks if the slices changed from fully-qualified to un-qualified or vice
versa.

The correct approach is to do what lookupAttribute for constraints does: check
both forms. Following the example set by lookupAttribute, fully-qualified is
given precedence in case of a conflict.

2026-10-07 08:29:37 +02:00

..

metrics

Pass individual informers, move DRA controllers to resource.go, simplify retry logic and metric tests

2026-03-19 16:50:03 +02:00

controller_test.go

Lock DRADeviceTaints and DRADeviceTaintRules feature gates to GA in 1.38, remove in 1.41

2026-09-18 12:48:46 -04:00

controller.go

kube-controller-manager: use context-aware client-go

2026-09-07 16:49:09 +02:00

doc.go

Add ResourcePoolStatusRequest controller, registry, and RBAC

2026-03-19 16:50:02 +02:00

views_test.go

DRA resource pool status request (#140170)

2026-07-22 15:05:52 +00:00

views.go

DRA consumable capacity: fix allocation result lookup

2026-10-07 08:29:37 +02:00