![]() The endpoint controllers responded to Pod changes by trying to figure out if the generated endpoint resource would change, rather than just checking if the Pod had changed, but since the set of Pod fields that need to be checked depend on the Service and Node as well, the code ended up only checking for a subset of the changes it should have. In particular, EndpointSliceController ended up only looking at IPv4 Pod IPs when processing Pod update events, so when a Pod went from having no IP to having only an IPv6 IP, EndpointSliceController would think it hadn't changed. |
||
---|---|---|
.. | ||
BUILD | ||
controller_utils_test.go | ||
controller_utils.go | ||
OWNERS | ||
trigger_time_tracker_test.go | ||
trigger_time_tracker.go |