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

Reserved UDP Port Range for NodePort Services #47723

Open
marty-power opened this issue Aug 29, 2024 · 7 comments
Open

Reserved UDP Port Range for NodePort Services #47723

marty-power opened this issue Aug 29, 2024 · 7 comments
Assignees
Labels
language/en Issues or PRs related to English language needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/network Categorizes an issue or PR as relevant to SIG Network.

Comments

@marty-power
Copy link

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:

| TCP | Inbound | 30000-32767 | NodePort Services† | All |

/sig network

@k8s-ci-robot k8s-ci-robot added sig/network Categorizes an issue or PR as relevant to SIG Network. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 29, 2024
@k8s-ci-robot
Copy link
Contributor

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 triage/accepted label.

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.

@dipesh-rawat
Copy link
Member

Page related to issue: https://kubernetes.io/docs/reference/networking/ports-and-protocols/

/language en

@k8s-ci-robot k8s-ci-robot added the language/en Issues or PRs related to English language label Aug 29, 2024
@Adarsh-verma-14
Copy link
Contributor

For a node port Service, Kubernetes additionally allocates a port (TCP, UDP or SCTP to match the protocol of the Service).
this is mention here about UDP protocols:https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport

@Adarsh-verma-14
Copy link
Contributor

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/

@Adarsh-verma-14
Copy link
Contributor

I want to work on that if triage accepted .

@sftim
Copy link
Contributor

sftim commented Sep 3, 2024

/priority backlog

I haven't checked if UDP NodePorts use the same range as TCP.

@k8s-ci-robot k8s-ci-robot added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Sep 3, 2024
@ayushpatil2122
Copy link
Contributor

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
language/en Issues or PRs related to English language needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Development

No branches or pull requests

6 participants