IP address requirements

Node IP addresses must not change during cluster operation. To replace a cluster node, remove it from the cluster, then add it back with a new address. For scaling cluster nodes, see the guide.

Control Plane node requirements #

Control Plane node IP addresses must belong to the same data network broadcast segment and subnet.

Virtual IP address requirements #

IP addresses are required for use as virtual addresses for the Kube-API server and Ingress when no external load balancer is used.

1. Two virtual IP addresses (VIPs) are required for a single cluster; they must not be configured on any cluster node.
2. The first VIP must belong to the same subnet as Control Plane node IP addresses. It is used for the cluster API server.
3. The second VIP (for Ingress) is used on the network load balancer.
4. For a management cluster with one Control Plane node, IP addresses must be assigned in strictly ascending order following this sequence: node IP address, then API server VIP, then Ingress VIP.

Correct: 
Node IP address - 11.11.11.2
API server VIP - 11.11.11.3
Ingress VIP - 11.11.11.4

Incorrect:
Node IP address - 11.11.11.4
API server VIP - 11.11.11.2
Ingress VIP - 11.11.11.3