Release Notes
Announcements
Release Notes
Solution | VPC-CNI (recommended) | Global Router | Cilium-Overlay |
Introduction | Pod network addresses are divided from VPC subnet addresses. It is recommended that they use a subnet exclusively. VPC cloud network capabilities such as Elastic IP (EIP), Cloud Load Balancer (CLB), and security groups are available. | The Pod IP range is independent of the VPC subnet IP range. Pods on different nodes can directly access each other through global routing and forwarding. | The container network and node network are not on the same plane. The container network is an overlay network based on the node network. |
Strengths | CIDR blocks do not need to be assigned by node, avoiding the waste of IP addresses. Data plane forwarding does not require a network bridge, which improves network forwarding performance. Pods can be assigned fixed IP addresses. This mode is suitable for scenarios that require containers to have fixed IP addresses. | The container IP range is independent of the VPC CIDR block. This solution is easy to use, with a quick Pod startup. | The container IP range is independent of the VPC CIDR block, with ample addresses and high scalability. Pod networks encapsulate messages with VxLAN. This solution is suitable for interconnection between cloud nodes and off-cloud nodes, with better compatibility. |
Scenarios | Scenarios with high requirements for network latency. Scenarios where the migration of the traditional architecture to a container platform requires the container to have a fixed IP address. Businesses with special network security policies. For example, database services require special security group policies. | Simple business scenarios with no special requirements for IP address assignment and network performance. Scenarios where nodes do not support ENI. | Only suitable for scenarios with registered nodes. |
Use Limits | The container network and node network belong to the same VPC network. IP address resources are limited. The number of containers in a node is limited by ENI and the number of assignable IP addresses. The fixed IP address mode does not support scheduling Pods with fixed IP addresses across availability zones (AZs). | The container network address cannot conflict with the node network address. Additional configuration is required in interconnection scenarios such as Direct Connect, Peering Connection, and Cloud Connect Network (CCN). Fixed Pod IP addresses are not supported. | Pod IP addresses cannot be accessed directly outside the cluster. Two IP addresses need to be obtained from the specified subnet to create a private network CLB instance, so that registered nodes in the IDC can access API servers and public cloud services. Fixed Pod IP addresses are not supported. |
Whether the Direct Connection of CLB Is Supported | Supported (allowlist application required). For details, see Using Services with CLB-to-Pod Direct Access Mode. | Not supported. | |
Whether Fixed IP Addresses Are Supported | Supported. | Not supported. | Not supported. |
IPv4/IPv6 Dual-Stack | Supported. | Not supported. | Not supported. |
Specifying Subnets for IP Address Assignment | Supported. | Not supported. | Not supported. |
Expanding Pod IP Ranges | Supported. | Supported (not productized yet). | Not supported. |
Setting a Pod Security Group | Supported. | Not supported. | Not supported. |
Binding EIP to a Pod | Supported. | Not supported. | Not supported. |
Pod Access to the Public Network | Supported (NAT and EIP). | Supported (IP address disguise). | Supported. |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback