Updated on 2025-06-13 GMT+08:00

Cluster Type

Type

CCE Standard

CCE Turbo

CCE Autopilot

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, networks, and scheduling

Serverless clusters without user nodes, no node deployment, management, and security maintenance, billed by actual CPU and memory usage

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

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

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 model
  • VPC network model

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

A maximum of 2000 nodes is supported.

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

hostPort

Supported

Not 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.

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

Network isolation

  • Tunnel network model: network policies supported for communications within a cluster
  • VPC network model: 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.

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.

VM-level isolation

Edge infrastructure management

Not supported

Management of CloudPond edge sites

Not supported