Skip to content
New issue

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

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

Already on GitHub? # to your account

Kubernetes ingress 1.11.5 version issue Gateway timeout via ingress route #13144

Closed
Chandini218chandu opened this issue Mar 31, 2025 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@Chandini218chandu
Copy link

What happened?

Hi Team,

I have a ingress controller version 1.11.5. I face gateway timeout issue and super slow when ever i route my applications via ingress.
I deleted webhook and tried still that doesn't help.

What did you expect to happen?

I would need a fast routing with out any issues

How can we reproduce it (as minimally and precisely as possible)?

I deployed ingress on internal network hence the ingress internal ingress load balancer.

Anything else we need to know?

No response

Kubernetes version

ingress 1.11.5
kubernetes 1.31

Cloud provider

azure

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

@Chandini218chandu Chandini218chandu added the kind/bug Categorizes issue or PR as related to a bug. label Mar 31, 2025
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Mar 31, 2025
@k8s-ci-robot
Copy link
Contributor

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

  • /sig <group-name>
  • /wg <group-name>
  • /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

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.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Mar 31, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject 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.

@BenTheElder
Copy link
Member

ingress 1.11.5

This appears to be an ingress-nginx version, this is the wrong repo.
/transfer ingress-nginx

@k8s-ci-robot k8s-ci-robot transferred this issue from kubernetes/kubernetes Apr 2, 2025
@Gacko
Copy link
Member

Gacko commented Apr 2, 2025

Please open a new issue in the correct project and fill the issue template you're facing upon creation. Thank you!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Development

No branches or pull requests

4 participants