Kubernetes has multiple levels of timeouts for calls, including at the load balancer, inbound to the ingress itself, and at the individual ingress resources.
Assuming you have the first two configured and are still hitting a timeout on your app, this is the annotation you need to add to your service’s ingress resource to boost its timeout:
nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
This will change it up to 1 hour from 1 minute.
When you are using the (nginx) ingress resource in kubernetes, you may want to view the actual configuration it is running, even though you are fairly abstracted from it. It can be very useful for debugging complex issues.
You can run these two lines to get the config file into a local nginx.conf file for inspection when you need to:
POD=$(kubectl get pods -n kube-system | grep ingress | awk '{print $1}')
kubectl exec -it -n kube-system ${POD} cat /etc/nginx/nginx.conf > nginx.conf
Coding Stream of Consciousness 