Skip to content

Backport of Removing peer state connectServices not in exported-service-list into release/1.22.x#23412

Merged
pajay-rao merged 2 commits intorelease/1.22.xfrom
backport/peer-serviceresolver-failover-1/globally-desired-lemming
Apr 1, 2026
Merged

Backport of Removing peer state connectServices not in exported-service-list into release/1.22.x#23412
pajay-rao merged 2 commits intorelease/1.22.xfrom
backport/peer-serviceresolver-failover-1/globally-desired-lemming

Conversation

@hc-github-team-consul-core
Copy link
Copy Markdown
Collaborator

Backport

This PR is auto-generated from #23377 to be assessed for backporting due to the inclusion of the label backport/1.22.

The below text is copied from the body of the original PR.


Description

Removing peer state connectServices not in exported-service-list.
Not removing it stops deletion of old cached connectServices and its event version causing subsequent stream propagation on scale up of the service.

Testing & Reproduction steps

Links

PR Checklist

  • updated test coverage
  • external facing docs updated
  • appropriate backport labels added
  • not a security concern

PCI review checklist

  • I have documented a clear reason for, and description of, the change I am making.

  • If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.

  • If applicable, I've documented the impact of any changes to security controls.

    Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.


Overview of commits

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved Consul Bot automated PR

@pajay-rao pajay-rao requested review from a team as code owners April 1, 2026 04:21
@pajay-rao pajay-rao merged commit 8ff7003 into release/1.22.x Apr 1, 2026
103 of 104 checks passed
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.

3 participants