Tencent Kubernetes Engine (TKE) provides two network modes, GlobalRouter and VPC-CNI, for different scenarios. This article gives a detailed introduction to the two network modes, as well as comparisons on applicable scenarios, advantages, and use limits.
GlobalRouter is a global routing capability provided by TKE based on the underlying VPC instance. It implements a mutual access routing policy between the container network and the VPC instance. This network mode has the following characteristics:
The GlobalRouter mode is suitable for general use cases and can be seamlessly used with standard Kubernetes features. The following diagram illustrates how it works:
VPC-CNI is a container network capability provided by TKE based on CNIs and VPC ENIs. It is ideal for scenarios with demanding latency requirements. In this network mode, containers and nodes are located on the same network plane, and container IP addresses are ENI IP addresses assigned by the IPAMD component.
The following diagram illustrates how the VPC-CNI mode works:
- This feature is in beta now. To apply for this, please submit a ticket.
- By default, the VPC-CNI mode does not support static pod IP addresses. You can set this capability only when creating a cluster and cannot modify it after the cluster is created.
- With static pod IP addresses enabled, you can only choose an empty subnet to set up the cluster network.
- Pods with static IP addresses cannot be migrated across subnets.
In the step where you configure "Cluster Information", select VPC-CNI for "Container network plugin" and select "Enable", as shown below:
For information on how to use the VPC-CNI mode with static pod IP addresses, see Managing StatefulSets with Static IP Addresses.
This section compares GlobalRouter and VPC-CNI on dimensions of applicable scenarios, advantages, and use limits. You can choose the network mode that best fits your needs.
|Additional Capabilities||Standard Kubernetes features|