<p>When a request takes over 60s to respond it seems that the ingress controller will bounce </p>

<p>From what I can see our NGINX ingress controller returns 504 to the client after a request takes more than 60s to process.  I can see this from the NGINX logs:</p>

<pre><code>2019/01/25 09:54:15 [error] 2878#2878: *4031130 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.244.0.1, server: myapplication.com, request: "POST /api/text HTTP/1.1", upstream: "http://10.244.0.39:45606/api/text", host: "myapplication.com"
10.244.0.1 - [10.244.0.1] - - [25/Jan/2019:09:54:15 +0000] "POST /api/text HTTP/1.1" 504 167 "-" "PostmanRuntime/7.1.6" 2940 60.002 [default-myapplication-service-80] 10.244.0.39:45606 0 60.000 504 bdc1e0571e34bf1223e6ed4f7c60e19d
</code></pre>

<p>The second log item shows 60 seconds for both <strong>upstream response time</strong> and <strong>request time</strong> (see <a href="https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/log-format.md" rel="noreferrer">NGINX log format here</a>)</p>

<p>But I have specified all the timeout values to be 3 minutes in the ingress configuration:</p>

<pre><code>apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: aks-ingress
  annotations:
    kubernetes.io/ingress.class: nginx
    certmanager.k8s.io/cluster-issuer: letsencrypt
    nginx.ingress.kubernetes.io/rewrite-target: /
    nginx.ingress.kubernetes.io/send_timeout: "3m"
    nginx.ingress.kubernetes.io/proxy-connect-timeout: "3m"
    nginx.ingress.kubernetes.io/proxy-read-timeout: "3m"
    nginx.ingress.kubernetes.io/proxy-send-timeout: "3m"
spec:
  tls:
  - hosts:
    - myapplication.com
    secretName: tls-secret
  rules:
  - host: myapplication.com
    http:
      paths:
      - path: /
        backend:
          serviceName: myapplication-service
          servicePort: 80
</code></pre>

<p>What am I missing?</p>

<p>I am using nginx-ingress-1.1.0 and k8s 1.9.11 on Azure (AKS).</p>

Dave New
<p>The issue was fixed by provided integer values (in seconds) for these annotations:</p>

<pre><code>nginx.ingress.kubernetes.io/proxy-connect-timeout: "180"
nginx.ingress.kubernetes.io/proxy-read-timeout: "180"
nginx.ingress.kubernetes.io/proxy-send-timeout: "180"
</code></pre>

<p>It seems that <a href="https://github.com/kubernetes/ingress-nginx" rel="noreferrer">this variation</a> of the NGINX ingress controller requires such.</p>
