Setting Communication Between Cluster Container and IDC
Last updated: 2020-01-02 14:40:08PDF
Currently, a container cluster can communicate with your IDC mainly through two methods: Direct Connect and IPsec VPN.
- This document uses a cluster that has been created and a node that has been added as an example. For more information about how to create a cluster, see Creating a Cluster.
- Please make sure that the VPC where your TKE service is located has been successfully connected with your IDC via a Direct Connect line or VPN.
Communication over Direct Connect
- Apply for a physical Direct Connect line as instructed in Applying for a Physical Direct Connect Line.
- Apply for a tunnel as instructed in Applying for a Tunnel.
- Create a Direct Connect gateway as instructed in Creating a Direct Connect Gateway.
- Verify that the container node can communicate with the IDC.
When performing this step, please make sure that the container node can communicate with the IDC and the verification is successful.
- Prepare information such as the region, appID, cluster ID, vpcID, and Direct Connect gateway ID and submit a ticket to open up the container network.
- Select the mode of operation based on the type of protocol used by the IDC.
- If the IDC uses the BGP protocol, the container IP address range route will be automatically synchronized.
- If other protocols are used, you need to configure the next hop of the container IP address range in the IDC to be routed to the Direct Connect gateway.
- Verify that the container can communicate with the IDC.
Communication over VPN
Configuring an SPD Policy
- Log in to the VPC console.
- In the left sidebar, click VPN > VPN tunnel to go to the VPN tunnel management page.
- Click the ID/name of the local VPN tunnel for which the SPD policy needs to be configured. See the figure below:
- On the VPN tunnel details page, click Edit in the "SPD policy" column to add the container IP address range. See the figure below:
- Click Save.
- Repeat step 3 to step 5 to configure the SPD policy for the opposite VPN tunnel.
Adding a Container IP Address Range
One subnet can be bound to only one routing table. If multiple routing tables are associated, they will be replaced with the last bound one.
- In the left sidebar, click Routing Table to go to the routing table management page.
- Find the routing table configured when setting intra-region cross-cluster communication or setting cross-region cross-cluster communication. Click the ID/name of the routing table to go to the routing table details page.
- Click + Create a routing policy to append the container IP address range.
- Select the Associate a subnet tab and click Create an associated subnet to associate the subnet where the server is located.
- Repeat step 2 to step 4 to add the IP address range where the Tencent Cloud container is located to the opposite routing device.
Containers can communicate with opposite servers. See the figure below:
Containers can communicate with VPN opposite servers.
If you want your cloud containers to communicate with your IDC over an IPsec VPN, you need to set the SPD policy and routing table.