Comparison Between Cluster Types

Positioning

Standard clusters that provide highly reliable and secure containers for commercial use

Next-generation clusters designed for Cloud Native 2.0, with accelerated compute, networking, and scheduling

Application scenario

For users who expect to use container clusters to manage applications, obtain elastic compute resources, and enable simplified management on compute, network, and storage resources

For users who have higher requirements on performance, resource utilization, and full-scenario coverage

Network model

Cloud native 1.0 networks: for scenarios where requirements on performance are not high and there are not so many containers

• Tunnel network
• Virtual Private Cloud (VPC) network

Cloud Native 2.0 networks: for scenarios where there are many containers and need high performance

A maximum of 2000 nodes is supported.

hostPort

Supported

Not supported

Network performance

The container network is overlaid with the VPC network, causing certain performance loss.

The VPC network and container network are flattened into one for zero performance loss.

Network isolation

• Tunnel networks: network policies for communications within a cluster
• VPC networks: isolation not supported

Pods can be associated with security groups for isolation. This isolation policy, based on security groups, ensures consistent security isolation both within and outside a cluster.

Container resource isolation

cgroups are used to isolate common containers.

• VM-level isolation is supported for secure containers that run only on physical machines.
• cgroups are used to isolate common containers.

Edge infrastructure management

Not supported

Management of CloudPond edge sites