Configuring a Default Container Subnet for a CCE Turbo Cluster

Updated on 2025-02-18 GMT+08:00

View PDF

If the pod subnet configured during CCE Turbo cluster creation cannot meet service expansion requirements, you can add a pod subnet for the cluster.

Log in to the CCE console and access the CCE Turbo cluster console.
On the Overview page, locate the Networking Configuration area and click Add.

Figure 1 Adding a pod subnet
Select a pod subnet in the same VPC. You can add multiple pod subnets at a time. If no other pod subnet is available, go to the VPC console and create one.

Figure 2 Selecting a pod subnet
Click OK.

NOTE:

Pod subnets can be deleted from clusters of v1.23.17-r0, v1.25.12-r0, v1.27.9-r0, v1.28.7-r0, v1.29.3-r0, or later versions.

Log in to the CCE console and access the CCE Turbo cluster console.
On the Settings page, click the Network tab.
In the Container Network area, click Update in the Operation column of default-network (Default Container Subnet).
In the Pod Subnet area, deselect the subnets to be deleted and click OK.
NOTICE:
- Deleting a pod subnet is risky. Make sure that no ENI in the cluster is using the subnet that you plan to delete. This includes ENIs that are being used by pods and prebound ENIs in the cluster.
  To find out if any ENIs are being used by a cluster, copy the ID of the subnet that you plan to delete. Then, use this ID to filter the ENIs and sub-ENIs associated with the VPC subnet on the Network Interfaces tab page. If the name or description of any of the filtered ENIs contains a cluster ID, then those ENIs are being used by the cluster.
- After a subnet is deleted, the security group of the cluster node will not automatically remove the rules associated with the subnet. Make sure that no ENIs in the cluster are still using the subnet and manually clear these rules that are associated with it.