Peering Connection provides high-bandwidth, high-quality data links connecting Tencent Cloud resources. With Peering Connection, you can implement . For more information, refer to Creating Peering Connections.
- The directions in this document are based on an existing cluster with nodes. If you don't have one, please refer to Creating Clusters.
- Make sure that the peering connection is successfully created and the CVM instances can communicate with one another. If the peering connection does not work, go to the console and check if the route table, CVM security groups, and subnet ACL are configured properly.
To implement interconnection between cross-region clusters, submit a ticket after completing the following steps to configure container routing to interconnect containers.
Getting container information
- Log in to the TKE console and select Cluster in the left sidebar.
- Click the ID/name of the cluster for which to set cluster interconnection to enter the management page of the cluster.
- In the left sidebar, select "Basic information" to go to the "Basic information" page.
- Record the following information: Region, Node Network, and Container Network.
- Repeat step 3 to step 5 for the other container in the different cluster.
For example, you can record the information of the container in Cluster B.
Configuring route tables
- Log in to the VPC console and select Peering Connection on the left sidebar.
- In the peering connection management page, record the name/ID of the peering connection.
- Select Subnet on the left sidebar to enter the subnet management page.
- Click the local end of the peering connection and specify the routing table associated with the subnet.
- On the Default Details page of the associated route table, click + New routing policies.
- In the Add a route page, configure the following parameters:
- Destination: Enter the IP address range of the container in Cluster B.
- Next hop type: Select Peering connection.
- Next hop: Select the established peering connection.
- Click OK to complete the configuration of the local route table.
- Repeat step 3 to step 7 to configure the route table of the opposite end.
- Intro-region peering: the above directions should allow containers in different clusters to communicate.
- Cross-region cluster: after the peering connection is established successfully, submit a ticket to configure container routing to interconnect the containers.
Refer to Basic Remote Terminal Operations on how to log in to a container, and verify the peering connection as instructed below:
- Log in to the container in Cluster A and access the container in Cluster B.
- Log in to the container in Cluster B and access the container in Cluster A.