-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Reserved UDP Port Range for NodePort Services #47723
Comments
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the The 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. |
Page related to issue: https://kubernetes.io/docs/reference/networking/ports-and-protocols/ /language en |
|
Kubernetes expects the port range 30000-32767 to be reserved for both TCP and UDP NodePort services as of my thinking so need to add UDP documentation here:https://kubernetes.io/docs/reference/networking/ports-and-protocols/ |
I want to work on that if triage accepted . |
/priority backlog I haven't checked if UDP NodePorts use the same range as TCP. |
/assign |
The Ports and Protocols documentation currently describes the port range of 30000-32767 as being reserved only for TCP NodePort services. Kubernetes also uses this range for allocating UDP NodePort services, however this is undocumented. Does Kubernetes expect this range of UDP ports to be reserved as well?
Docs:
website/content/en/docs/reference/networking/ports-and-protocols.md
Line 31 in 1c5221a
/sig network
The text was updated successfully, but these errors were encountered: