Pod CIDR Reservation

Check Items

Check if pod CIDR reservation is enabled. Enable this function to prevent new subnet CIDR blocks from conflicting with pod CIDR blocks.

Clusters v1.28.15-r70, v1.29.15-r30, v1.30.14-r30, v1.31.10-r30, v1.32.6-r30, v1.33.5-r20, and later support pod CIDR reservation. If any cluster does not support this function, upgrade the cluster to the target version and then enable this function.

This check item is only performed for clusters using the VPC network. For clusters using other network models, skip this check item.

Solutions

1. Log in to the CCE console and click the cluster name to access the cluster console.
2. In the navigation pane, choose Settings. On the Network tab, check the pod CIDR reservation settings.
   • If pod CIDR reservation is not enabled, enable it for the cluster.
   • If this function fails to be enabled, confirm the conflicting route based on the error information and evaluate whether to rectify the fault. For details, see Common Issues.
     

     If this function fails to be enabled, the cluster can still be used normally.

Common Issues

If the error information shown in the figure is displayed, the reserved route 172.17.0.0/16 fails to be added due to a conflict.

Update vpc container CIDRs reservation failed: update routeTable(*** add route:[172.17.0.0/16] and del rout[], failed: unexpected response code [400] when accessing [PUT https://vpc.***.com/v1/***/routetables/***] in request [***],response body: [{"code":"VPC.2812","message":"The destination of route to add is existalready."}]

Troubleshooting: Search for the conflicting network segment in the default route and check whether rectification is required.

1. In the Network Information area on the Overview page, view the VPC used by the cluster and click the VPC name to go to the VPC console.
2. Click the number in the Route Tables column to view the route tables of the VPC.

   

3. Click the default route table name to go to the route details page.

   

4. Query the conflicting route based on the destination address in the error information and evaluate the rectification impact.