Cloud Connect Network (CCN) provides interconnection among Virtual Private Clouds (VPCs) and between VPCs and local IDCs. You can add VPCs and Direct Connect gateway instances to the CCN to achieve single-point access and network-wide resource sharing for a simple, intelligent, secure, and flexible hybrid cloud and globally interconnected network.
You can register existing container clusters to CCN, and CCN will include the containers’ network in its scope of management. After the containers’ network is fully registered, you can enable or disable the IP range routing of the containers’ network on the CCN side to achieve interconnection between the container clusters and resources in CCN.
After a container cluster is registered to CCN, its IP range will be enabled when it does not conflict with the existing routing in the CCN instance, and it will be disabled by default when there are conflicts.
This step only registers the container IP range to the CCN. Whether or not the routing takes effect depends on your configuration on the CCN side.
- 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 on routing conflicts, see Use Limit > Route Restrictions. If you want to enable a route that may lead to routing conflicts, read Enabling a Route.