-
Notifications
You must be signed in to change notification settings - Fork 688
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
Add configuration support to tune or disable listener Keepalives. #2652
Comments
xref #2543 |
@jpeach on #2638 you said "I don't know of any use case for supporting Envoy on non-Linux" and I agree. Until such a use case exists can we not just update https://projectcontour.io/resources/envoy/ to say that we only support running Envoy on Linux? |
Yeh, though the corollary of that is that it's probably fine to have an emergency knob rather than implementing this for various platform. |
This change allows users to tune envoy's keepalive settings. Fixes projectcontour#2652 Fixes projectcontour#3214 Signed-off-by: binoue <banji-inoue@cybozu.co.jp>
This change allows users to tune envoy's keepalive settings. Fixes projectcontour#2652 Fixes projectcontour#3214 Signed-off-by: binoue <banji-inoue@cybozu.co.jp>
…ettings This change allows users to tune envoy's keepalive settings. Fixes projectcontour#2652 Fixes projectcontour#3214 Signed-off-by: binoue <banji-inoue@cybozu.co.jp>
This change allows users to tune envoy's keepalive settings. Fixes projectcontour#2652 Fixes projectcontour#3214 Signed-off-by: binoue <banji-inoue@cybozu.co.jp>
As we may be moving to support Envoy/Contour running on Windows, this cross-platform issue will come up again |
Please describe the problem you have
Followup from #2638 #2633
If the Envoy proxy that Contour is programming isn't running on Linux, it will NACK the listener update, and Contour won't know how to recover from that. In this case, an operator would need a way to disable setting Linux-specific socket options.
There may be use cases for tweaking the Listener keep alive tunables. We can collect implementation experience here.
The text was updated successfully, but these errors were encountered: