Port requirements for cluster communication

Review port requirements for Cortex XSOAR 8.13 On-prem.

The following ports are required for standalone (one VM) and a three-node cluster (three VMs).

Port	Protocol	Purpose
22	TCP	SSH communication
8880	TCP	Node communication
2049	TCP	Backup and restore server communication
111	TCP	Backup and restore server communication

Required control plane ports

A Kubernetes cluster consists of a control plane and one or more worker nodes. For Cortex XSOAR, in standalone (one VM), the VM acts as both the control plane and a worker node. In multi-node clusters, the first three nodes act as both control plane and worker nodes, and any additional node added acts as a worker node.

The following ports are required for a control plane. They are open only between the nodes in the cluster. For standalone, none of these ports are required.

Name	Port	Protocol
etcd client port	2379	TCP
etcd peer port	2380	TCP
Kubernetes API	6443	TCP
Kubelet API	10250	TCP
kube-scheduler	10257	TCP
kube-controller-manager	10259	TCP

Required worker node port

The following port is required for a worker node. It is open only between the nodes in the cluster.

Name	Port	Protocol
kube nodeport range	30000:32767	TCP

Intra-node communication

The following port is required for a multi-node cluster (three VMs). It is open only between the nodes in the cluster. It is not required for standalone.

Name	Port	Protocol
Calico with IPv4 Wireguard	51820	UDP