mirror of https://github.com/k3s-io/k3s
cfdaf18277
Automatic merge from submit-queue Fix potential panic in namespace controller when rapidly create/delet… Fixes https://github.com/kubernetes/kubernetes/issues/33676 The theory is this could occur in either of the following scenarios: 1. HA environment where a GET to a different API server than what the WATCH was read from 1. In a many controller scenario (i.e. where multiple finalizers participate), a namespace that is created and deleted with the same name could trip up the other namespace controller to see a namespace with the same name that was not actually in a delete state. Added checks to verify uid matches across retry operations. /cc @liggitt @kubernetes/rh-cluster-infra |
||
|---|---|---|
| .. | ||
| certificates | ||
| daemon | ||
| deployment | ||
| disruption | ||
| endpoint | ||
| garbagecollector | ||
| informers | ||
| job | ||
| namespace | ||
| node | ||
| petset | ||
| podautoscaler | ||
| podgc | ||
| replicaset | ||
| replication | ||
| resourcequota | ||
| route | ||
| scheduledjob | ||
| service | ||
| serviceaccount | ||
| volume | ||
| .import-restrictions | ||
| BUILD | ||
| OWNERS | ||
| client_builder.go | ||
| controller_ref_manager.go | ||
| controller_utils.go | ||
| controller_utils_test.go | ||
| doc.go | ||
| lookup_cache.go | ||