reverse_conn: envoy contrib changes for reverse_connection custom cluster #37932
Conversation
This file contains 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
…ster Signed-off-by: Basundhara Chakrabarty <[email protected]>
|
Hi @basundhara-c, welcome and thank you for your contribution. We will try to review your Pull Request as quickly as possible. In the meantime, please take a look at the contribution guidelines if you have not done so already. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Commit Message: This PR defines a new custom cluster type "envoy.clusters.reverse_connection" which enables requests to be sent over reverse connections instead of forward connections. This PR is strictly tied with #37368.
Additional Description: In order to differentiate between requests that need to be sent via a reverse connection vs those to be sent through forward connections, a new cluster type has been defined. The downstream requests to be sent over reverse connections are expected to contain either of the HTTP headers defined in the cluster's typed config, to enable upstream envoy to figure out which downstream node to send the request to,
The Cluster Manager checks whether the connection is intended for a reverse connection cluster, and if so, calls a custom HTTP/2 conn pool to send the request over the reverse connection.
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]