fec25785ee
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. |
||
|---|---|---|
| .. | ||
| metrics | ||
| controller_test.go | ||
| controller.go | ||
| doc.go | ||
| OWNERS | ||
| uid_cache.go | ||