Nginx Ingress To Not Timeout when backend takes time to respond

[hk250097]

What happened:

Hey there,

When using Nginx Ingress in GCP, I'm experiencing a timeout issue with long response times, causing a 504 gateway timeout on the client side. I think NGINX using default 60 seconds timeout.
Error on the client side: 504 Gateway Timeout

What you expected to happen:
We want to set the timeout to 90 seconds and let NGINX not re try when backend takes longer duration.
Lets say backend takes more than 90 seconds, let NGINX not retry as backend may be down.
So we don't want NGINX to retry again instead return 504.
Is there a config to let Ingress-Nginx know to retry in specific use cases and not to re try in specific use cases.

NGINX retries for 3 times to backend. Which is causing additional request's.
We know the backend is down and not able to responsd. We don't want additional request's to backend.

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[longwuyuan]

/remove-kind bug
/triage needs-information

Can you answer the questions that are asked in a new bug report template.

[hk250097]

Got the information what's needed.

[Nomis742]

Got the information what's needed.

Can you tell us how you solved the problem? I am facing the same issue.