Updated on 2026-08-29 GMT+08:00

Cluster Overview

Cloud Container Engine (CCE) is a Kubernetes cluster hosting service for enterprises. It manages the entire lifecycle of containerized applications and delivers scalable, high-performance solutions for deploying and managing cloud native applications.

Cluster Types

  • CCE standard clusters are for commercial use. They fully support the standard features of open-source Kubernetes clusters. Management and O&M of master nodes are not necessary. Depending on the service scenarios, you can choose to use either the container tunnel network model or the VPC network model. This cluster type is suitable for general scenarios without specific performance or scale requirements.
  • CCE Turbo clusters run on the Cloud Native 2.0 infrastructure. They feature hardware and software synergy, zero network performance loss, high security and reliability, and intelligent scheduling, offering you a one-stop, cost-effective container service. The Cloud Native 2.0 networks are available for large-scale, high-performance scenarios. In a CCE Turbo cluster, pod IP addresses are assigned from the VPC CIDR block, and pods and nodes can be in different subnets. External networks in the VPC can directly access pod IP addresses for high performance.

For details about the differences between these clusters, see Comparison Between Cluster Types.

Cluster Network

A cluster network consists of the following three networks:

  • Node network: assigns IP addresses to nodes in a cluster.
  • Container network: assigns IP addresses to containers in a cluster. Currently, multiple container network models are supported, and each model has its own operating principle.
  • Service network: assigns a fixed IP address to each Service used to access containers.

When you create a cluster, select an appropriate CIDR block for each network. Ensure that the CIDR blocks do not conflict with each other and have sufficient available IP addresses. You cannot change the container network model after the cluster is created. Select the right container network model in advance.

You are advised to learn about the cluster network and container network models before creating a cluster. For details, see Container Networks.

Number of Master Nodes in a Cluster and Cluster Scale

In a CCE cluster, the number of master nodes does not determine the cluster scale. They are two different aspects:

  • Master nodes: When creating a cluster on CCE, you have the option to choose one or three master nodes. If you choose three master nodes, the cluster will have high availability.
  • Cluster scale: refers to the maximum number of worker nodes that can be managed by a cluster. For example, you can choose a cluster management scale of 50 or 200 nodes when creating the cluster. The flavors of the master nodes are influenced by the cluster scale. Higher cluster scales require higher master node flavors.

    It is possible to change the cluster scale after creating the cluster. However, you can only increase the scale and cannot decrease it. For details, see Resizing a Cluster.

Cluster Lifecycle

Table 1 Cluster statuses

Status

Description

Creating

A cluster is being created and is requesting cloud resources.

Running

A cluster is running properly.

Hibernating

A cluster is hibernating.

Awaking

A cluster is waking up.

Upgrading

A cluster is being upgraded.

Resizing

The cluster flavor is being changed.

Unavailable

A cluster is unavailable.

Deleting

A cluster is being deleted.