Backport of state: ensure that identical manual virtual IP updates result in not bumping the modify indexes into release/1.20.x #21969
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.
Backport
This PR is auto-generated from #21909 to be assessed for backporting due to the inclusion of the label backport/1.20.
The below text is copied from the body of the original PR.
Description
The
consul-k8s
endpoints controller issues catalog register and manual virtual ip updates without first checking to see if the updates would be effectively not changing anything. This is supposed to be reasonable because the state store functions do the check for a no-op update and should discard repeat updates so that downstream blocking queries watching one of the resources don't fire pointlessly (and CPU wastefully).While this is true for the check/service/node catalog updates, it is not true for the "manual virtual ip" updates triggered by the
PUT /v1/internal/service-virtual-ip
. Forcing the connect injector pod to recycle while watching some lightly modified FSM code can show that a lot of updates are of theupdate list of ips from [A] to [A]
. Immediately following this stray update you can see a lot of activity inproxycfg
andxds
packages waking up due to blocking queries triggered by this.This PR skips updates that change nothing both:
Testing & Reproduction steps
consul-k8s
+kind
with 2 connect-enabled servicesPR Checklist
[ ] external facing docs updatedOverview of commits