Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "Fix destination staleness issue when adding EndpointSlices (#12427)" #12589

Merged
merged 1 commit into from
May 13, 2024

Conversation

alpeb
Copy link
Member

@alpeb alpeb commented May 13, 2024

This reverts commit 4fccf3e.

The early return was causing pp.addresses = newAddressSet to not be run when the list of addresses is empty; but setting that is still necessary so that labels are tracked correctly.

This was caught by the tap (viz) integration test run in the release workflow.

…12427)"

This reverts commit 4fccf3e.

The early return was causing `pp.addresses = newAddressSet` to not be run when the list of addresses is empty; but setting that is still necessary so that labels are tracked correctly.

This was caught by the tap (viz) integration test run in the release workflow.
@alpeb alpeb requested a review from a team as a code owner May 13, 2024 22:56
@alpeb alpeb changed the title Revert "Fix destination staleness issue when adding EndpointSlices (#12427) Revert "Fix destination staleness issue when adding EndpointSlices (#12427)" May 13, 2024
@adleong adleong merged commit 9bd8c00 into main May 13, 2024
36 checks passed
@adleong adleong deleted the alpeb/revert-12427 branch May 13, 2024 23:25
the-wondersmith pushed a commit to the-wondersmith/linkerd2 that referenced this pull request May 15, 2024
…inkerd#12427)" (linkerd#12589)

This reverts commit 4fccf3e.

The early return was causing `pp.addresses = newAddressSet` to not be run when the list of addresses is empty; but setting that is still necessary so that labels are tracked correctly.

This was caught by the tap (viz) integration test run in the release workflow.

(cherry picked from commit 9bd8c00)
the-wondersmith added a commit to the-wondersmith/linkerd2 that referenced this pull request May 15, 2024
* origin/policy-feat-grpcroute-status-support:
  chore(ci): merge fixes from origin/main
  build(deps): bump tj-actions/changed-files from 44.3.0 to 44.4.0 (linkerd#12588)
  build(deps): bump github.com/fatih/color from 1.16.0 to 1.17.0 (linkerd#12590)
  chore(ci): Remove conditional integration testing (linkerd#12591)
  build(deps-dev): bump sinon from 17.0.1 to 17.0.2 in /web/app (linkerd#12587)
  build(deps): bump github.com/prometheus/client_golang (linkerd#12586)
  build(deps): bump thiserror from 1.0.59 to 1.0.60 (linkerd#12585)
  Revert "Fix destination staleness issue when adding EndpointSlices (linkerd#12427)" (linkerd#12589)
  Add outbound index metrics to the policy controller (linkerd#12429)
  build(deps): bump tj-actions/changed-files from 44.3.0 to 44.4.0 (linkerd#12588)
  build(deps): bump github.com/fatih/color from 1.16.0 to 1.17.0 (linkerd#12590)
  chore(ci): Remove conditional integration testing (linkerd#12591)
  build(deps-dev): bump sinon from 17.0.1 to 17.0.2 in /web/app (linkerd#12587)
  build(deps): bump github.com/prometheus/client_golang (linkerd#12586)
  build(deps): bump thiserror from 1.0.59 to 1.0.60 (linkerd#12585)
  Revert "Fix destination staleness issue when adding EndpointSlices (linkerd#12427)" (linkerd#12589)
  Set backend_not_found route status when any backends are not found (linkerd#12565)
  Add outbound index metrics to the policy controller (linkerd#12429)

Signed-off-by: Mark S <[email protected]>
alpeb added a commit that referenced this pull request May 20, 2024
This is a second take on #12427, which avoided a theoretical/correctness
issue around overwritting new ES addresses with stale data.

We had to revert that in #12589 because the change introduced a bug, by
returning early when the ES had no addresses and failed to properly
initiallize `addesses` for the portPublisher.

This just removes the early return.
alpeb added a commit that referenced this pull request May 20, 2024
This is a second take on #12427, which avoided a theoretical/correctness
issue around overwritting new ES addresses with stale data.

We had to revert that in #12589 because the change introduced a bug, by
returning early when the ES had no addresses and failed to properly
initiallize `addesses` for the portPublisher.

This just removes the early return.
alpeb added a commit that referenced this pull request May 20, 2024
This is a second take on #12427, which avoided a theoretical/correctness
issue around overwritting new ES addresses with stale data.

We had to revert that in #12589 because the change introduced a bug, by
returning early when the ES had no addresses and failed to properly
initiallize `addesses` for the portPublisher.

This just removes the early return.
alpeb added a commit that referenced this pull request May 22, 2024
This is a second take on #12427, which avoided a theoretical/correctness
issue around overwritting new ES addresses with stale data.

We had to revert that in #12589 because the change introduced a bug, by
returning early when the ES had no addresses and failed to properly
initiallize `addesses` for the portPublisher.

This just removes the early return.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants