You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: