de02323a9d
This fixes a bug that occurred when a Service was rapidly recreated. This relied on an unfortunate series of events: 1. When the Service is deleted, the EndpointSlice controller removes it from the EndpointSliceTracker along with any associated EndpointSlices. 2. When the Service is recreated, the EndpointSlice controller sees that there are still appropriate EndpointSlices for the Service and does nothing. (They have not yet been garbage collected). 3. When the EndpointSlice is deleted, the EndpointSlice controller checks with the EndpointSliceTracker to see if it thinks we should have this EndpointSlice. This check was intended to ensure we wouldn't requeue a Service every time we delete an EndpointSlice for it. This adds a check in reconciler to ensure that EndpointSlices it is working with are owned by a Service with a matching UID. If not, it will mark those EndpointSlices for deletion (assuming they're about to be garbage collected anyway) and create new EndpointSlices. |
||
|---|---|---|
| .. | ||
| config | ||
| metrics | ||
| BUILD | ||
| endpointset.go | ||
| endpointslice_controller_test.go | ||
| endpointslice_controller.go | ||
| endpointslice_tracker_test.go | ||
| endpointslice_tracker.go | ||
| OWNERS | ||
| reconciler_test.go | ||
| reconciler.go | ||
| utils_test.go | ||
| utils.go | ||