Help Center/ Cloud Container Engine/ User Guide/ Clusters/ Buying a Cluster/ Comparison Between Cluster Types
Updated on 2026-05-26 GMT+08:00
View PDF
Share

Comparison Between Cluster Types

Comparison

CCE provides different types of clusters for you to select. The following table lists the differences between them.

Cluster Type

CCE standard

CCE Turbo

CCE Autopilot

Positioning

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

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

Serverless clusters that you do not need to manage nodes and are billed based on actual CPU and memory usage

In such clusters, no node deployment, management, and security maintenance are needed.

Applications

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

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

For users whose services suffer frequent traffic surges, such as users in the online education and e-commerce sectors

Network

For scenarios where there are not so many containers and high performance is not needed, the following networks are provided:

  • Tunnel networks
  • VPC networks

For details, see Network Model Comparison.

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

By default, 2,000 nodes are supported. A maximum of 20,000 nodes are supported.

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

Host Ports (hostPort) for Pods

Supported

Not supported by default; supported after DataPlane V2 is enabled

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.

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: NetworkPolicies are supported after DataPlane V2 is enabled. For details, see DataPlane V2.

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

After DataPlane V2 is enabled, CCE supports network policies. For details, see DataPlane V2.

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

Pod EIP

Not supported

Supported

Supported

Static Pod IP Address

Not supported

Supported by StatefulSets and can be combined with EIP binding to provide a fixed public IP address

Supported by StatefulSets and can be combined with EIP binding to provide a fixed public IP address

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.

VM-level isolation

Edge Infrastructure Management

Not supported

Support for management of edge cloud resources. For details, see Using Edge Cloud Resources in a Remote CCE Turbo Cluster.

Not supported
Parent Topic: Buying a Cluster