Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ingress Time outs after 2 minutes even though time out is set to 3600s #10726

Closed
kherath17 opened this issue Dec 4, 2023 · 3 comments
Closed

Ingress Time outs after 2 minutes even though time out is set to 3600s #10726

kherath17 opened this issue Dec 4, 2023 · 3 comments
Labels
needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@kherath17
Copy link

kherath17 commented Dec 4, 2023 •
edited
Loading

Issue Description

I have setup an ingress service to route requests to Selenium Grid , even though the requests are reached to grid que, it timeouts after 2 minutes , with below error response

<head><title>504 Gateway Time-out</title></head>
<body>
<center>504 Gateway Time-out</center>
</body>
</html>

Solutions tried

  • Added below annotations but still timeouts when reaching 2 minutes
    nginx.ingress.kubernetes.io/proxy-connect-timeout: "3600"
    nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
    nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"

Sample Ingress File

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: qlabv2-ingress
annotations:
`kubernetes.io/ingress.class: nginx
#nginx.ingress.kubernetes.io/app-root: /qlabv2
nginx.ingress.kubernetes.io/rewrite-target: /$2
nginx.ingress.kubernetes.io/use-regex: "true"
nginx.ingress.kubernetes.io/proxy-connect-timeout: "3600"
nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"
spec:
rules:
- http:
paths:
- path: /sandbox_qlabv2(/|$)(.)
pathType: Prefix
backend:
service:
name: selenium-hub-service
port:
number: 80
- path: /(/?)(session/./se/vnc)
pathType: Prefix
backend:
service:
name: selenium-hub-service
port:
number: 80
@kherath17 kherath17 added the kind/bug Categorizes issue or PR as related to a bug. label Dec 4, 2023
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Dec 4, 2023
@k8s-ci-robot
Copy link
Contributor

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/test-infra repository.

@longwuyuan
Copy link
Contributor

None of the questions asked in the new issue template have been answered so there is no way to get a good understanding of the problem.

Don't even know what the curl command for HTTP/HTTPS request sent was

And the description is not formatted as per markdown

Please fix all that to help a reader make some data based comments.

/remove-kind bug
/triage needs-information

@k8s-ci-robot k8s-ci-robot added triage/needs-information Indicates an issue needs more information in order to work on it. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. and removed kind/bug Categorizes issue or PR as related to a bug. labels Dec 5, 2023
@kherath17
Copy link
Author

Closing this and created new ticket with correct formatting #10735

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
[SIG Network] Ingress NGINX
Archived in project
Milestone
No milestone
Development

No branches or pull requests
3 participants
@longwuyuan @k8s-ci-robot @kherath17