-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does Envoy support per filter chain draining? #10899
Comments
Thanks @mattklein123. To clarify, per filter chain draining would work without needing Filter Discovery Service - using a listener with multiple filter chains would transparently drain connections per filter chain? |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions. |
@lambdai is there an update on this? |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions. |
Checking again. |
@shashankram I beleive filter chain draining is fixed. I read in some other issues. |
My understanding has been that if a Listener with multiple filter chains is configured and a filter chain within the listener is updated, connections belonging to other filter chains but the same listener are also drained. Is this still the case?
Looking at a few PRs, I see that there has been some effort to support per filter chain draining:
#9205
#4540
#7246
Is this feature supported now?
What is the recommended listener configuration to drain connections per filter chain? Is a Filter Discovery Service (FDS) required?
The text was updated successfully, but these errors were encountered: