'K8s Nginx Ingress in Rancher - Timeout not working

I have a service and pod(s) both working perfectly in my infrastructure with a simple ingress.

However there are a couple of cases which the front-end request a PDF generation of the backend that can take around 1,5 - 2seconds. While I said to the team developing that they should:

  • try to speed it up the process by making the code a bit leaner or
  • make it work differently by firing a request, asking if it is done in separate intervals and downloading it when ready (3 or more shortly lived requests)

They just can't do it now and I said I would do my best... to which is apparently not enough...

I have the following Ingress YAML:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: tool-ingress
  namespace: testing
  annotations:
    kubernetes.io/ingress.class: "nginx"
    nginx.ingress.kubernetes.io/proxy-connect-timeout: "600"
    nginx.ingress.kubernetes.io/proxy-send-timeout: "600"
    nginx.ingress.kubernetes.io/proxy-read-timeout: "600"
spec:
  rules:
  - host: tool.example.com
    http:
      paths:
      - pathType: ImplementationSpecific
        backend:
          service:
            name: tool-service
            port: 
              number: 80 
  tls:
  - hosts:
    - tool.example.com
    secretName: mySecret

Now I still keep getting a timeout in the browser after 1s. I've tried several variants but I can't get this to work. I have created the ingress directly on rancher but the yaml above I tried deploying directly with kubectl apply. Both variants did not change a thing.

QUESTION(s)

  • Is there something I am clearly missing?
  • Is this something I have to check/change on rancher that might be taking precedence over these values?
  • I've read in a lot of places that people go into the "generated ingress pod" and check the generated annotation but I don't see anything like a pod being created with my ingress
    • I do have the ingress-controllers on the ingress-nginx namespace but I thought they are for internally controlling the communication between the nodes on the cluster (I have a 3 node cluster) since I see one deployed on each cluster

Any pointers would be appreciated.

Info: K8s Rev: v1.19.6 Rancher Rev: v2.5.5



Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source