Cloud Connect Network (CCN) interconnects Virtual Private Clouds (VPCs) or VPCs and local IDCs. You can add VPCs and direct connect gateway instances to the CCN to enjoy single-point access and network-wide resource sharing. This way, you can build a simple, intelligent, secure, and flexible hybrid cloud and a globally interconnected network.
You can register existing container clusters to the CCN, and the CCN will manage the container network. After the container network is registered, you can enable or disable routes of the container network IP range on the CCN side to ensure interconnection between the container clusters and resources in CCN.
After a container cluster is registered to the CCN, its IP range will be enabled when it does not conflict with existing routes in the CCN instance, and it will be disabled by default when there are conflicts.
This step only registers the container’s IP range to the CCN. Whether the route takes effect depends on your configuration on the CCN side.
- If the IP range of the container network does not conflict with existing routes in the CCN instance, the route will be enabled by default. If there is an IP range conflict, the route will be disabled by default.
- For more information about route conflicts, see Use Limits. If you want to enable a route that may lead to conflicts, see Enabling a Route.
4. Test the interconnection between the container cluster and other resources in the CCN.