fix(discovery): when endpoint_slices
updated, old endpoints all flush_all/flush_expired
#11577
+3
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes # (endpoint muti slices)
Bad case:
If the number of nodes of a certain service is too large, for example, it is split into two endpoint slices:
slice1: There are
pod1
andpod2
.slice2: There are
pod3
andpod4
.If the pod is re-scheduled and only slice1 or slice2 is updated, the upstream will only be updated to
pod1
+pod2
orpod3
+pod4
.When
watch_endpoint_slices_schema
is true(endpoint_slice model), removeinformer.pre_list
andinformer.post_list
Checklist