kubernetes/pkg/controller/endpointslice
Antonio Ojea b8ba6ab005 endpointslices: node missing on Pod scenario
When a Pod is referencing a Node that doesn't exist on the local
informer cache, the current behavior was to return an error to
retry later and stop processing.
However, this can cause scenarios that a missing node leaves a
Slice stuck, it can no reflect other changes, or be created.
Also, this doesn't respect the publishNotReadyAddresses options
on Services, that considers ok to publish pod Addresses that are
known to not be ready.

The new behavior keeps retrying the problematic Service, but it
keeps processing the updates, reflacting current state on the
EndpointSlice. If the publishNotReadyAddresses is set, a missing
node on a Pod is not treated as an error.
2022-06-22 09:45:16 +02:00
..
config generated: Run hack/update-gofmt.sh 2021-08-24 15:47:49 -04:00
metrics fix metrics for placeholder slice 2022-06-22 09:45:02 +02:00
topologycache Updating TopologyCache to disregard unready endpoints in calculations 2021-11-18 13:54:09 -08:00
endpointslice_controller_test.go Fix unnecessary recreation of placeholder EndpointSlice 2022-06-14 09:24:38 -07:00
endpointslice_controller.go Merge pull request #109624 from aryan9600/fix-endpointslice-deletion 2022-06-09 00:11:42 -07:00
OWNERS Check in OWNERS modified by update-yamlfmt.sh 2021-12-09 21:31:26 -05:00
reconciler_test.go endpointslices: node missing on Pod scenario 2022-06-22 09:45:16 +02:00
reconciler.go endpointslices: node missing on Pod scenario 2022-06-22 09:45:16 +02:00
utils_test.go Stop publishing Pod ResourceVersion in Endpoints and EndpointSlice API 2022-03-02 22:12:35 +08:00
utils.go Stop publishing Pod ResourceVersion in Endpoints and EndpointSlice API 2022-03-02 22:12:35 +08:00