Backport of Fix route subscription when using namespaces into release/1.15.x #16680
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 #16677 to be assessed for backporting due to the inclusion of the label backport/1.15.
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
We’re improperly subscribing to our routes in the proxycfg package, leveraging the proxy enterprise metadata rather than the route metadata. This causes the gateway to never get configured when it binds a route in another namespace. This PR fixes that by ensuring the correct EnterpriseMeta is used to reference the namespace
Testing & Reproduction steps
In consul enterprise set up a two namespaces, a gateway in one namespace, a service in the other, and attempt to setup a httproute in the service namespace. The route will never register without this fix (also automated tests showing this are coming up in a follow up PR).
Links
N/A
PR Checklist
Overview of commits