Change:
For more details please see the [Network Plugin Requirements](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#network-plugin-requirements) page. ## Check required ports <del> ### Control-plane node(s) | Protocol | Direction | Port Range | Purpose                 | Used By                   | |----------|-----------|------------|-------------------------|---------------------------| | TCP      | Inbound   | 6443*      | Kubernetes API server   | All                       | | TCP      | Inbound   | 2379-2380  | etcd server client API  | kube-apiserver, etcd      | | TCP      | Inbound   | 10250      | kubelet API             | Self, Control plane       | | TCP      | Inbound   | 10251      | kube-scheduler          | Self                      | | TCP      | Inbound   | 10252      | kube-controller-manager | Self                      | ### Worker node(s) | Protocol | Direction | Port Range  | Purpose               | Used By                 | |----------|-----------|-------------|-----------------------|-------------------------| | TCP      | Inbound   | 10250       | kubelet API           | Self, Control plane     | | TCP      | Inbound   | 30000-32767 | NodePort Services†    | All                     | † Default port range for [NodePort Services](/docs/concepts/services-networking/service/). Any port numbers marked with * are overridable, so you will need to ensure any custom ports you provide are also open. Although etcd ports are included in control-plane nodes, you can also host your own etcd cluster externally or on custom ports. </del> <ins> These [required ports](/docs/reference/ports-and-protocols/) need to be open in order for Kubernetes components to communicate with each other. </ins> The pod network plugin you use (see below) may also require certain ports to be open. Since this differs with each pod network plugin, please see the

Discussion:
What would you like to be Create a dedicated ports and protocols page for Kubernetes Clusters. Why is this needed Currently, the closest page that provides this information is under KubeAdm install setup . This is hard to find for any cluster administrator trying to deploy Kubernetes Documented Ports for and are incorrect and need an update Slack thread: /sig security node docs architecture /area security
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : What would you like to be Create a dedicated ports and protocols page for Kubernetes Clusters. Currently, the closest page that provides this information is under KubeAdm install setup . This is hard to find for any cluster administrator trying to deploy Kubernetes Documented Ports for and are incorrect and need an update /area security Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage accepted
Hi Would you be OK to have this as a reference page, rather than as a concept?
/sig network
/sig cluster-lifecycle Given the PR touches kubeadm docs.
Moved it under . This was the kind of feedback I was looking for from SIG Docs. Thank you