How to Configure upstream Idle connection timeout on Consul Terminating Gateway?
Open
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 43
Description
**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?
Contributor guide
Assessment
This issue has not been assessed yet.