-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Comments
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! |
@vepatel Here it is. |
@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 |
Hi @saedx1 thanks for the issue and PR We'll discuss this in our next triage meeting and prioritise |
Why does a fix for an outstanding bug need to wait that long? |
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 is32767
.This is a bug, and it has nothing to do with NodePorts range.
The text was updated successfully, but these errors were encountered: