According to the planned network information for the workload cluster, configure the relevant network information.
Procedure
Configure the control plane VIP.
After configuration, as long as the node failure is within the allowed range, it is possible to access the available control plane nodes through this IP, even if there is a node failure in the control plane node group.
There are two configuration methods:
Assigned by IP pool: Select the workload cluster IP pool created based on the planning. The system will automatically allocate a control plane virtual IP from this IP pool.
Enter manually: Enter the control plane VIP you previously planned.
Configure the network for the workload cluster.
| Parameter | Description |
|---|---|
| Business-specific NIC | Select the VM network for the business-specific NIC and configure the IP address based on Network requirements for business-specific NICs . Two configuration methods are as follows:
|
| DNS server address (optional) | If the DNS server Information is not configured in the DHCP server, enter the specific DNS server address; otherwise, leave this field blank. Note that the DNS server address cannot be 127.0.0.1. |
| ABS CSI dedicated NIC (displayed only when ABS CSI addon is selected) |
|
| AIC dedicated NIC (displayed only when AIC CNI is selected) | Based on the information planned according to the network requirements for AIC NIC , fill in the network, subnet CIDR, gateway, and Pod IP CIDR. |
Configure the Service IP CIDR and Pod IP CIDR. This network segment cannot overlap with the network segment used by the cluster network and cannot use public IP addresses. Different clusters can use the same network segment for Service IP CIDR and Pod IP CIDR.
| Parameter | Description |
|---|---|
| Service IP CIDR | Enter a range of IP addresses for Service usage. |
| Pod IP CIDR | Only required when the selected CNI addon is Calico. You need to enter a range of IP addresses for pod usage. |
Click Next.