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.
If you need cross-region peering, please complete the following directions and submit a ticket to apply for container interconnection through routing.
Getting container information
- Log in to the TKE console and select Clusters from the left sidebar.
- Click the ID/name of the desired cluster to go to its cluster management page.
The following is the cluster management page of Cluster A.
- Select Basic Information from the left sidebar 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 from the left sidebar.
- In the peering connection management page, record the name/ID of the peering connection.
- Select Subnet from the left sidebar to go to the subnet management page.
- Click the route table associated with the desired subnet.
- On the 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. This completes the configuration of route table at the local end.
- 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 peering: after creation of the peering connection, submit a ticket to apply for container interconnection through routing.
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.