Configuring networks

According to the network information for the workload cluster, configure the relevant network information.

Procedure

1. Configure the control plane VIP.

   After configuring this VIP, as long as it is within the allowed failure 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: The system automatically allocates a control plane VIP from the created workload cluster IP pool.

   • Enter manually: Enter the control plane VIP you previously planned.

2. 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 the business-specific NICs . Two configuration methods are as follows: Assigned by IP pool Enable NIC DHCP
   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. The DNS server address cannot be 127.0.0.1.
   ABS CSI NIC (Only shows when ABS CSI is selected)	If planning to use the storage of the ACOS cluster where the VM-based workload cluster is located, ensure ABS CSI access configuration is created . Once done, the system will automatically fill in network and access VIP information. You only need to select the IP pool created for accessing this ACOS cluster, which is dedicated to the ABS CSI NIC. If planning to use storage from other clusters for the VM-based workload cluster, select the VM network used by the ABS CSI NIC of the cluster nodes according to the actual plan, fill in the access VIP of the target storage cluster, and select the IP pool created for the ABS CSI NIC to access the target storage cluster. Note: The access VIP cannot be modified after the VM-based workload cluster is created.
   AIC NIC (Only shows when AIC CNI is selected)	Based on Network requirements for AIC NIC , fill in Network, Subnet CIDR, Gateway, and Pod IP CIDR.

3. Configure the Service IP CIDR and Pod IP CIDR. This range 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.

4. Click Next.