Backport of Peering Mesh Gateway Updates for GA into release/1.14.x #15363
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 #15344 to be assessed for backporting due to the inclusion of the label backport/1.14.
WARNING automatic cherry-pick of commits failed. Commits will require human attention.
The below text is copied from the body of the original PR.
Description
Follow up to #15340. This branch was based on that one, so all new changes are in the most recent commit.
Adding content for control-plane traffic for peering through mesh gateways. I realized that the concept of mesh gateways was tied pretty strongly to WAN fed in the docs, so I attempted to extract the general mesh gateway content from the specific wan-fed/peering setup.
I don't love some of the organization but hoping we can come back and optimize after the 1.14 release.
Overview of commits