Enabling Cross-VPC Network Communications Between CCE Clusters

Assume that the local VPC CIDR block is 172.16.0.0/16 and the peer VPC CIDR block is 172.17.0.0/16. To configure a route table, take the following steps:

1. In the lower part of the VPC peer connection details page, click Add Route. The Add Route dialog box is displayed.
   Figure 3 Adding routes for the VPC peering connection
   

2. Add routes to the VPC CIDR blocks at both ends in the route tables as instructed. Table 2 describes the parameters.

   Table 2 Adding routes to both VPC CIDR blocks

   Parameter	Description	Example Value
   VPC	Select a VPC that is connected by the VPC peering connection.	vpc-A
   Route Table	Select the route table of the VPC. The route will be added to this route table. Each VPC comes with a default route table to control the outbound traffic from the subnets in the VPC. In addition to the default route table, you can create a custom route table and associate it with the subnets in the VPC. Then, the custom route table controls outbound traffic of the subnets. If there is only the default route table in the drop-down list, select the default route table. If there are both default and custom route tables in drop-down list, select the route table associated with the subnet connected by the VPC peering connection.	rtb-vpc-A (Default route table)
   Destination	IP address in the VPC at the other end of the VPC peering connection. The value can be a VPC CIDR block, subnet CIDR block, or ECS IP address.	vpc-B CIDR block: 172.17.0.0/16
   Next Hop	The default value is the current VPC peering connection. You do not need to specify this parameter.	peering-AB
   Description	Supplementary information about the route. This parameter is optional. The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).	Route from vpc-A to vpc-B
   Add a route for the other VPC	If you select this option, you can also add a return route for the other VPC of the VPC peering connection. To allow VPCs connected through VPC peering to communicate, you must include forward and return routes in the VPCs' route tables.	Select this option.
   VPC	By default, the system selects the other VPC connected by the VPC peering connection. You do not need to specify this parameter.	vpc-B
   Route Table	Select the route table of the VPC that the route will be added to. Each VPC comes with a default route table to control the outbound traffic from the subnets in the VPC. In addition to the default route table, you can also create a custom route table and associate it with the subnets in the VPC. Then, the custom route table controls outbound traffic of the subnets. If there is only the default route table in the drop-down list, select the default route table. If there are both default and custom route tables in drop-down list, select the route table associated with the subnet connected by the VPC peering connection.	rtb-vpc-B (Default route table)
   Destination	IP address in the VPC at the other end of the VPC peering connection. The value can be a VPC CIDR block, subnet CIDR block, or ECS IP address.	vpc-A CIDR block: 172.16.0.0/16
   Next Hop	The default value is the current VPC peering connection. You do not need to specify this parameter.	peering-AB
   Description	Supplementary information about the route. This parameter is optional. The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).	Return route from vpc-B to vpc-A.

3. After configuring the routes, click OK and go back to the route list. You can view the added routes.

Assume that the local VPC CIDR block is 172.16.0.0/16, the peer VPC CIDR block is 172.17.0.0/16, and the container CIDR block of the cluster is 10.0.0.0/16. To configure a route table, take the following steps:

1. In the lower part of the VPC peer connection details page, click Add Route. The Add Route dialog box is displayed.
   Figure 4 Adding routes for the VPC peering connection
   

2. Add routes to the VPC CIDR blocks at both ends in the route tables as instructed. Table 3 describes the parameters.

   Table 3 Adding routes to both VPC CIDR blocks

   Parameter	Description	Example Value
   VPC	Select a VPC that is connected by the VPC peering connection.	vpc-A
   Route Table	Select the route table of the VPC. The route will be added to this route table. Each VPC comes with a default route table to control the outbound traffic from the subnets in the VPC. In addition to the default route table, you can create a custom route table and associate it with the subnets in the VPC. Then, the custom route table controls outbound traffic of the subnets. If there is only the default route table in the drop-down list, select the default route table. If there are both default and custom route tables in drop-down list, select the route table associated with the subnet connected by the VPC peering connection.	rtb-vpc-A (Default route table)
   Destination	IP address in the VPC at the other end of the VPC peering connection. The value can be a VPC CIDR block, subnet CIDR block, or ECS IP address.	vpc-B CIDR block: 172.17.0.0/16
   Next Hop	The default value is the current VPC peering connection. You do not need to specify this parameter.	peering-AB
   Description	Supplementary information about the route. This parameter is optional. The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).	Route from vpc-A to vpc-B
   Add a route for the other VPC	If you select this option, you can also add a return route for the other VPC of the VPC peering connection. To allow VPCs connected through VPC peering to communicate, you must include forward and return routes in the VPCs' route tables.	Select this option.
   VPC	By default, the system selects the other VPC connected by the VPC peering connection. You do not need to specify this parameter.	vpc-B
   Route Table	Select the route table of the VPC that the route will be added to. Each VPC comes with a default route table to control the outbound traffic from the subnets in the VPC. In addition to the default route table, you can also create a custom route table and associate it with the subnets in the VPC. Then, the custom route table controls outbound traffic of the subnets. If there is only the default route table in the drop-down list, select the default route table. If there are both default and custom route tables in drop-down list, select the route table associated with the subnet connected by the VPC peering connection.	rtb-vpc-B (Default route table)
   Destination	IP address in the VPC at the other end of the VPC peering connection. The value can be a VPC CIDR block, subnet CIDR block, or ECS IP address.	vpc-A CIDR block: 172.16.0.0/16
   Next Hop	The default value is the current VPC peering connection. You do not need to specify this parameter.	peering-AB
   Description	Supplementary information about the route. This parameter is optional. The route description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).	Return route from vpc-B to vpc-A.

3. After configuring the routes, click OK and go back to the route list. You can view the added routes.
4. Click Add Route and add the route of the container CIDR block of the cluster to the VPC route tables by referring to Table 4.
   Figure 5 Adding routes of the container CIDR block of a cluster
   

   Table 4 Configuring route parameters

   Parameter	Example Value
   VPC	vpc-A
   Route Table	rtb-vpc-A (Default route table)
   Destination	In this example, the container CIDR block of the cluster is 10.0.0.0/16.
   Next Hop	peering-AB
   Description	Route from vpc-A to vpc-B
   Add a route for the other VPC	Select this option.
   VPC	vpc-B
   Route Table	rtb-vpc-B (Default route table)
   Destination	In this example, the container CIDR block of the cluster is 10.0.0.0/16.
   Next Hop	peering-AB
   Description	Return route from vpc-B to vpc-A.

5. Click OK.