reverse_tunnel: add per-node connection limit#45612
Draft
aakugan wants to merge 1 commit into
Draft
Conversation
Signed-off-by: aakugan <aakashganapathy2@gmail.com>
|
CC @envoyproxy/api-shepherds: Your approval is needed for changes made to |
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
2 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.
Commit Message
reverse_tunnel: add per-node connection limit
Description
Add an optional safety cap on the number of concurrently accepted reverse tunnels per node. The cap (max_connections_per_node) is configured on the UpstreamReverseConnectionSocketInterface bootstrap extension, which owns the connection accounting shared across filters, and enforcement is opted into per filter via enable_connection_limit.
Defaults to disabled.
Testing
Unit and integ tests.