Repository navigation
reverse_tunnel: reject new streams during listener drain - #47446
AntonKanug wants to merge 1 commit into
Conversation
3fbedcf to
4d67d09
Compare
|
CC @envoyproxy/api-shepherds: Your approval is needed for changes made to |
4d67d09 to
4456fa8
Compare
Signed-off-by: Anton Kanugalawattage <antonk@palantir.com>
4456fa8 to
082dbd5
Compare
|
/assign basundhara-c |
|
/retest |
|
@agrawroh can you have a final look? |
|
/wait |
|
/assign aakugan |
|
aakugan cannot be assigned to this issue. |
|
/assign aakugan |
|
aakugan is not allowed to assign users. |
|
This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
|
This pull request has been automatically closed because it has not had activity in the last 37 days. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
Continued in #49361.
Stop reverse-tunnel initiators from creating or replacing tunnels when their listener starts draining, including pending handshakes. Close unused tunnels with drain-aware HCM enabled, while preserving replacement behavior for in-place filter-chain updates and normal connection rotation.
Preserve the current METADATA and GOAWAY schedule. Once GOAWAY arrives, responders exclude initiators whose remaining tunnels are all draining from new-stream selection while existing streams finish within the listener drain window.
Updated with AI assistance.