<p><code>OpenShift 4.6</code></p>
<p>There is a basic set up in OpenShift: [Pod &lt;- Service &lt;- Route].
A service running in the pod have an HTTP endpoint responding for 90 seconds or longer. And in some cases it is normal, so I would like to allow this behavior.</p>
<p>Nevertheless, after a request to the route is sent (and a response did not arrive back) some time later (approx. 60-70 seconds) route responds with <code>HTTP 504</code>:</p>
<pre><code>&lt;html&gt;
&lt;body&gt;
    &lt;h1&gt;504 Gateway Time-out&lt;/h1&gt;
    The server didn't respond in time.
&lt;/body&gt;
&lt;/html&gt;
</code></pre>
<p>I am not sure at what point OpenShift decides to break the circuit and I can't find any configuration options that allow to change this timeout.</p>
<p><strong>How to set custom timeout for a service and a pod to extend duration of request-response cycle?</strong></p>

<p>You might be looking for the <code>haproxy.router.openshift.io/timeout</code> annotation, with which you can annotate your Route:</p>
<pre><code>oc annotate route myroute --overwrite haproxy.router.openshift.io/timeout=2s
</code></pre>
<p>You can find more information about Route configuration in the documentation: <a href="https://docs.openshift.com/container-platform/4.6/networking/routes/route-configuration.html#nw-configuring-route-timeouts_route-configuration" rel="nofollow noreferrer">https://docs.openshift.com/container-platform/4.6/networking/routes/route-configuration.html#nw-configuring-route-timeouts_route-configuration</a></p>
