CCE Turbo Clusters and CCE Standard Clusters

Positioning

-

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

Next-gen container cluster designed for Cloud Native 2.0, with accelerated computing, networking, and scheduling

Application scenario

-

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

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

Specification difference

Network model

Cloud-native network 1.0: applies to common, smaller-scale scenarios.

• Tunnel network
• Virtual Private Cloud (VPC) network

Cloud Native Network 2.0: applies to large-scale and high-performance scenarios.

Max networking scale: 2,000 nodes

Network performance

Overlays the VPC network with the container network, causing certain performance loss.

Flattens the VPC network and container network into one, achieving zero performance loss.

Network isolation

• Tunnel network model: supports network policies for intra-cluster communications.
• VPC network model: supports no isolation.

Associates pods with security groups. Unifies security isolation in and out the cluster via security groups' network policies.

Security isolation

Runs common containers, isolated by cgroups.

• Physical machine: runs Kata containers, allowing VM-level isolation.
• VM: runs common containers, isolated by cgroups.

Edge infrastructure management

None

Supports management of Intelligent EdgeSite (IES).