Cloud Connect Network (CCN) provides interconnection among Virtual Private Clouds (VPCs) and between VPCs and local IDCs. You can add VPCs and Direct Connect gateways to CCN to achieve single-point access and network-wide resource sharing for a simple, intelligent, secure, and flexible hybrid cloud and globally interconnected network.
Overview
You can register existing container clusters with CCN, and CCN will include the container network into its scope of management. After the container network is fully registered, you can enable or disable the IP range routing of the container network on the CCN side to achieve interconnection between the container clusters and resources in CCN.
Note
After a container cluster is registered with CCN, its IP range will be enabled if the IP range does not conflict with the existing routing in the CCN instance, and will be disabled by default if conflicts exist.
Prerequisites
The VPC of the cluster is already in CCN. For more information about the operations related to CCN, see Operations Overview.
You have evaluated whether the IP range of the cluster network conflicts with the IP ranges of other resources in CCN.
Directions
Registering Container Network to CCN
1. Log in to the TKE console and click Cluster in the left sidebar.
2. Click the ID of the cluster you want to register with CCN, and click Basic information on the left to go to the cluster basic information page.
3. Turn on the CCN registration switch to register the container network with CCN as shown below:
Note
This step registers only the container IP range to CCN. Whether or not the routing takes effect depends on your configuration on the CCN side.
Viewing the IP Range Routing of the Container
1. Log in to the VPC console and click CCN in the left sidebar to go to the CCN management page.
2. Click Manage instances to the right of the CCN associated with the cluster VPC to go to the CCN instance management page as shown below:
3. Click the Route table tab to view whether IP range routing is enabled for the container as shown below:
Note
If the IP range of the cluster network does not conflict with the existing routing in the CCN instance, the routing will be enabled by default. If there is an IP range conflict, the routing will be disabled by default.
For more information about routing conflicts, see Use Limits > Route Limits. If you want to enable a route that may lead to routing conflicts, see Enabling Route.
4. Test the interconnection between the container cluster and other resources in CCN.
