title: istio-proxy closing long running TCP connection after 1 hour
body: <p>TL;DR: How can we configure istio sidecar injection/istio-proxy/envoy-proxy/istio egressgateway to allow long living (&gt;3 hours), possibly idle, TCP connections?</p>
  <p>Some details:</p>
  <p>We're trying to perform a database migration to PostgreSQL which is being triggered by one application which has Spring Boot + Flyway configured, this migration is expected to last ~3 hours.</p>
  <p>Our application is deployed inside our kubernetes cluster, which has configured istio sidecar injection. After exactly one hour of running the migration, the connection is always getting closed.</p>
  <p>We're sure it's istio-proxy closing the connection as we attempted the migration from a pod without istio sidecar injection and it was running for longer than one hour, however this is not an option going forward as this may imply some downtime in production which we can't consider.</p>
  <p>We suspect this should be configurable in istio proxy setting the parameter idle_timeout - which was implemented <a href="https://github.com/istio/istio/pull/13515" rel="noreferrer">here</a>. However this isn't working, or we are not configuring it properly, we're trying to configure this during istio installation by adding <code>--set gateways.istio-ingressgateway.env.ISTIO_META_IDLE_TIMEOUT=5s</code> to our helm template.</p>