[NET-9098] Narrow scope of peering config on terminating gw filter chain to TCP services #21054
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.
Description
This narrows the scope of changes made previously in #19881 which have unintentionally impacted http config on terminating gateway filter chains
Testing & Reproduction steps
Run the consul-k8s peering acceptance test with transparent proxy and CNI flavors using a build of this consul-enterprise branch. The test that is currently broken should pass with this build.
Example:
There are existing xDS golden tests that cover TCP services. Those updates can be seen in #19881.
Additionally, we have followup work to add tcp-specific peering acceptance test coverage where there isn't any today. This is followup work so that we can go ahead and unblock the failing tests and upcoming release over in the consul-k8s repo.
Links
Example acceptance test failure in consul-k8s
PR Checklist