kubernetes/pkg/controller/resourceclaim
Patrick Ohly fec25785ee dra: store generated ResourceClaims in cache
This addresses the following bad sequence of events:
- controller creates ResourceClaim
- updating pod status fails
- pod gets retried before the informer receives
  the created ResourceClaim
- another ResourceClaim gets created

Storing the generated ResourceClaim in a MutationCache ensures that the
controller knows about it during the retry.

A positive side effect is that ResourceClaims now get index by pod owner and
thus iterating over existing ones becomes a bit more efficient.
2023-07-11 14:23:49 +02:00
..
metrics kube-controller-manager: add ResourceClaim controller 2022-11-10 20:23:50 +01:00
controller.go dra: store generated ResourceClaims in cache 2023-07-11 14:23:49 +02:00
controller_test.go dra: store generated ResourceClaims in cache 2023-07-11 14:23:49 +02:00
doc.go kube-controller-manager: add ResourceClaim controller 2022-11-10 20:23:50 +01:00
OWNERS kube-controller-manager: add ResourceClaim controller 2022-11-10 20:23:50 +01:00
uid_cache.go kube-controller-manager: add ResourceClaim controller 2022-11-10 20:23:50 +01:00