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.

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

[Bug]: Ingress Exposed Port Upper Limit is 32767 #7063

Open
saedx1 opened this issue Jan 6, 2025 · 5 comments
Open

[Bug]: Ingress Exposed Port Upper Limit is 32767 #7063

saedx1 opened this issue Jan 6, 2025 · 5 comments
Labels
bug An issue reporting a potential bug needs triage An issue that needs to be triaged

Comments

@saedx1
Copy link
Contributor

saedx1 commented Jan 6, 2025

Version

4.0.0

What Kubernetes platforms are you running on?

EKS Amazon

Steps to reproduce

This is straightforward, the maximum exposed port number you can set on an ingress through nginx.org/listen-ports* annotations is 32767.

This is a bug, and it has nothing to do with NodePorts range.

@saedx1 saedx1 added bug An issue reporting a potential bug needs triage An issue that needs to be triaged labels Jan 6, 2025
Copy link

github-actions bot commented Jan 6, 2025

Hi @saedx1 thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!

@saedx1
Copy link
Contributor Author

saedx1 commented Jan 6, 2025

@vepatel Here it is.

@saedx1
Copy link
Contributor Author

saedx1 commented Jan 6, 2025

@vepatel So, to respond to your comment on the PR. This should have nothing to do with the NodePort. This just adds on the listening ports in an nginx listen directive in a server block. Your examples, code, and tests are not mentioning anything about the NodePort range (nor they should) and they are not using the NodePort range exclusivly.

@vepatel
Copy link
Contributor

vepatel commented Jan 6, 2025

Hi @saedx1 thanks for the issue and PR

We'll discuss this in our next triage meeting and prioritise

@saedx1
Copy link
Contributor Author

saedx1 commented Jan 6, 2025

Why does a fix for an outstanding bug need to wait that long?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An issue reporting a potential bug needs triage An issue that needs to be triaged
Projects
Status: Todo ☑
Development

No branches or pull requests

2 participants