<p>I need to increase my traefik ingress timeouts because now I'm getting 499 errors.</p>

<p>When I was using Nginx as my ingress proxy as was able to use theses annotations:</p>

<pre><code>appVersion: ..
kind: Ingress
...
metadata:
  annotations:
    nginx.ingress.kubernetes.io/proxy-connect-timeout: "123"
    nginx.ingress.kubernetes.io/proxy-read-timeout: "456"
    nginx.ingress.kubernetes.io/proxy-send-timeout: "789"
</code></pre>

<p>but now I'm struggling to find alternatives to do in Traefik.</p>

<p>So what are the annotations to increase my ingress read, write, connect values?</p>

EdvinasPocius
<p>If I am not wrong, you are looking for feature that currently does not exist, but I found an appropriate feature request: <a href="https://github.com/containous/traefik/issues/3027" rel="nofollow noreferrer">Feature: Timeout override per backend #3027</a>.</p>

<p>It is in the open state since Mar 15, 2018.</p>

<p>However in the same topic I found fresh interesting for you information:</p>

<blockquote>
  <p>it is now possible to configure timeouts for each entrypoint in v2</p>
  
  <p><a href="https://docs.traefik.io/routing/entrypoints/#transport" rel="nofollow noreferrer">https://docs.traefik.io/routing/entrypoints/#transport</a></p>
</blockquote>

<p>So please refer to <a href="https://docs.traefik.io/routing/entrypoints/#transport" rel="nofollow noreferrer">Transport</a> section to get latest info and take a look from time to time on above feature request.</p>

<blockquote>
  <p>respondingTimeouts¶ respondingTimeouts are timeouts for incoming
  requests to the Traefik instance. Setting them has no effect for UDP
  entryPoints.</p>
</blockquote>

<p>1) <strong>transport.respondingTimeouts.readTimeout</strong></p>

<p>Optional, Default=0s</p>

<p>readTimeout is the maximum duration for reading the entire request, including the body.</p>

<p>If zero, no timeout exists.
Can be provided in a format supported by time.ParseDuration or as raw values (digits). If no units are provided, the value is parsed assuming seconds.</p>

<pre><code>## Static configuration
entryPoints:
  name:
    address: ":8888"
    transport:
      respondingTimeouts:
        readTimeout: 42
</code></pre>

<p>2) <strong>transport.respondingTimeouts.writeTimeout</strong></p>

<p>Optional, Default=0s</p>

<p>writeTimeout is the maximum duration before timing out writes of the response.</p>

<p>It covers the time from the end of the request header read to the end of the response write. If zero, no timeout exists.
Can be provided in a format supported by time.ParseDuration or as raw values (digits). If no units are provided, the value is parsed assuming seconds.</p>

<pre><code>## Static configuration
entryPoints:
  name:
    address: ":8888"
    transport:
      respondingTimeouts:
        writeTimeout: 42
</code></pre>

<p>3) <strong>transport.respondingTimeouts.idleTimeout</strong></p>

<p>Optional, Default=180s</p>

<p>idleTimeout is the maximum duration an idle (keep-alive) connection will remain idle before closing itself.</p>

<p>If zero, no timeout exists.
Can be provided in a format supported by time.ParseDuration or as raw values (digits). If no units are provided, the value is parsed assuming seconds.</p>

<pre><code>## Static configuration
entryPoints:
  name:
    address: ":8888"
    transport:
      respondingTimeouts:
        idleTimeout: 42
</code></pre>

<p>Hope that helps</p>
