Backport of fix: populate legacy service port at RPC boundaries into release/2.0.x - #23841
Open
hc-github-team-consul-core wants to merge 1 commit into
Conversation
hc-github-team-consul-core
force-pushed
the
backport/sanikachavan/fix-multi-port-rpc-backcompat/apparently-vast-gecko
branch
from
August 19, 2026 13:59
31b1eaa to
36f80f0
Compare
github-team-consul-core-pr-approver
approved these changes
Aug 19, 2026
github-team-consul-core-pr-approver
left a comment
github-team-consul-core-pr-approver
left a comment
Collaborator
There was a problem hiding this comment.
Auto approved Consul Bot automated PR
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 #23833 to be assessed for backporting due to the inclusion of the label backport/2.0.
The below text is copied from the body of the original PR.
Description
Testing & Reproduction steps
Links
PR Checklist
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