Port Requirements¶

To ensure proper operation, certain ports need to be opened. If firewall rules are configured on the network, it is necessary to ensure that the infrastructure components can communicate with each other through specific ports. Ensure that the following ports are open on the network and configured to allow access between hosts. Some ports are optional depending on the configuration and usage.

Bootstrap Node¶

Kube Clusters (Including Global Cluster and Worker Cluster)¶

Both the global cluster and the worker cluster are deployed through Kubean, so they need to open the same ports. In addition to the standard K8s ports, ports need to be opened for CNI and some network components.

K8s Control Plane¶

All K8s Nodes¶

Each node in the cluster needs to open these ports.

Refer to the Kubernetes Port and Protocol Documentation.

Calico (Default)¶

Calico is used as the CNI by default, and all K8s nodes need to open these ports.

Refer to the Calico Network Requirements Documentation.

MetalLB (Default)¶

When MetalLB is enabled to create VIPs, all K8s nodes need to open these ports.

Cilium (Optional)¶

If Cilium is used as the CNI, all K8s nodes need to open these ports.

Refer to the Cilium System Requirements Documentation.

SpiderPool (Optional)¶

If SpiderPool is used as the CNI, all K8s nodes need to open these ports.

Refer to the documentation: spiderpool-controller and spiderpool-agent.

KubeVIP (Optional)¶

When KubeVIP is enabled to create the Kube API VIP, all Control Plane nodes need to open these ports.

Other Ports to be Opened in the Global Management Cluster¶

Istio-Gateway VIP¶

Insight VIP¶

Other Ports to be Opened in the Worker Cluster¶

The worker cluster needs to open port 6443 for K8s API access by the global management cluster. If the deployment function is used, port 22 also needs to be opened for access by the global cluster.

Other Ports to be Opened by Other Products¶

Container Registry¶

Comments