Skip to content
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

How to Configure upstream Idle connection timeout on Consul Terminating Gateway? #21807

Open
shashank201192 opened this issue Oct 7, 2024 · 0 comments

Comments

@shashank201192
Copy link

Overview: We are using Consul's terminating gateway to connect to external service. External service is hosted behind AWS infrastructure where TCP Idle session timeout is 350 seconds and can't be changed. As per envoy's documentation https://www.envoyproxy.io/docs/envoy/latest/faq/configuration/timeouts , Default Idle connection timeout is 1 hour. Due to envoy having higher Idle connection timeout, we are seeing connection problems where upstream connection simply stops responding until client close the connection.

Ask: Is there a way to configure Idle connection timeout for upstreams(i.e, external services) in Terminating Gateway?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant