Buying a CCE Standard/Turbo Cluster

Type

Select CCE Standard Cluster or CCE Turbo Cluster as required.

For more details, see cluster types.

Billing Mode

Cluster Name

Enter a cluster name. Cluster names under the same account must be unique.

Enterprise Project

This parameter is available only for enterprise users who have enabled an enterprise project.

After an enterprise project is selected, clusters and their security groups will be created in that project. To manage clusters and other resources like nodes, load balancers, and node security groups, you can use the Enterprise Project Management Service (EPS).

Cluster Version

Select the Kubernetes version used by the cluster.

Cluster Scale

Select a cluster scale for your cluster as required. These values specify the maximum number of nodes that can be managed by the cluster.

Master Nodes

Select the number of master nodes. The master nodes are automatically hosted by CCE and deployed with Kubernetes cluster management components such as kube-apiserver, kube-controller-manager, and kube-scheduler.

VPC

Select the VPC to which the cluster belongs. If no VPC is available, click Create VPC to create one. The value cannot be changed after the cluster is created.

Node Subnet

Select the subnet to which the master nodes belong. If no subnet is available, click Create Subnet to create one. The value cannot be changed after the cluster is created.

Default Node Security Group

IPv6

If enabled, cluster resources, including nodes and workloads, can be accessed through IPv6 CIDR blocks.

Network Model

Select VPC network or Tunnel network for your CCE standard cluster.

Select Cloud Native Network 2.0 for your CCE Turbo cluster.

For more information about their differences, see Overview.

DataPlane V2 (supported by CCE Turbo clusters)

DataPlane V2 uses eBPF to enable features like Service ClusterIP, NetworkPolicy, and egress bandwidth. For details, see DataPlane V2 Network Acceleration.

This function is available for new clusters of v1.27 or later. After this function is enabled, CCE will automatically deploy the cilium-agent on every node in the cluster. Each cilium-agent will use 80 MiB of memory, and the memory usage will increase by 10 KiB whenever a new pod is added. After the cluster is created, you cannot disable this function. Additionally, the nodes can run only HCE OS 2.0. Therefore, enable this function only when you fully understand the constraints in DataPlane V2 Network Acceleration.

Network Policies (supported by CCE standard clusters using a tunnel network)

Policy-based network control for clusters. For details, see Configuring Network Policies to Restrict Pod Access.

After this function is enabled, if the CIDR blocks of a customer's service conflict with the on-premises CIDR blocks, the link to a newly added gateway may not be established.

For example, when a cluster accesses an external address through a Direct Connect connection, the external switch does not support ip-option. If the network policy is enabled, the network access may fail.

Container CIDR Block

Specify the CIDR block for containers, which determines the maximum number of containers allowed in the cluster. This parameter is available only for CCE standard clusters. CCE standard clusters allow both manual and automatic CIDR block settings.

Pod IP Addresses Reserved for Each Node (supported by CCE standard clusters using a VPC network)

Specify the number of container IP addresses that can be allocated to each node (alpha.cce/fixPoolMask) when creating a cluster. This parameter determines the maximum number of pods that can be created on each node and cannot be changed after the cluster is created.

When a container network is used, each pod occupies one IP address. If a node's reserved container IP addresses are insufficient, pods cannot be created. For details, see Number of Allocatable Container IP Addresses on a Node.

Pod Subnet

Select the subnet to which the pod belongs. If no subnet is available, click Create Subnet to create one. This parameter is available only for CCE Turbo clusters. The pod subnet determines the maximum number of containers in a cluster. You can add pod subnets after a cluster is created.

Default Security Group

Service CIDR Block

Configure the Service CIDR blocks for containers in the same cluster to access each other. The value determines the maximum number of Services you can create. The value cannot be changed after the cluster is created.

Request Forwarding

Select IPVS or iptables for your cluster. For details, see Comparing iptables and IPVS.

IPv6 Service CIDR Block

Configure this parameter only when IPv6 dual stack is enabled for a CCE Turbo cluster. This configuration cannot be modified after the cluster is created.

IAM Authentication

CCE clusters support IAM authentication. You can call IAM authenticated APIs to access CCE clusters.

Certificate Authentication

CPU Management

If enabled, exclusive CPU cores can be allocated to workload pods. For details, see CPU Policy.

Secret Encryption

The value cannot be changed after the cluster is created. For details, see Using KMS to Encrypt Secrets.

Overload Control

After this function is enabled, concurrent requests will be dynamically controlled based on the resource demands received by master nodes to ensure the stable running of the master nodes and the cluster. For details, see Enabling Overload Control for a Cluster.

Cluster Deletion Protection

A measure taken to prevent accidental deletion of clusters through the console or APIs. After this function is enabled, you will not be able to delete or unsubscribe from clusters on CCE. You can modify the function status in the cluster Settings after creating it.

Time Zone

The cluster's scheduled tasks and nodes are subject to the chosen time zone.

Resource Tag

You can add resource tags to classify resources. A maximum of 20 resource tags can be added.

Description

You can enter description for the cluster. A maximum of 200 characters are allowed.

CCE Container Network (Yangtse CNI)

This is the basic cluster add-on. It provides network connectivity, Internet access, and security isolation for pods in your cluster.

CCE Container Storage (Everest)

This add-on (CCE Container Storage (Everest)) is installed by default. It is a cloud native container storage system based on CSI and supports cloud storage services such as EVS.

CoreDNS

This add-on (CoreDNS) is installed by default. It provides DNS resolution for your cluster and can be used to access the in-cloud DNS server.

NodeLocal DNSCache

(Optional) If selected, this add-on (NodeLocal DNSCache) will be automatically installed. NodeLocal DNSCache improves cluster DNS performance by running a DNS caching agent on cluster nodes.

Volcano Scheduler

(Optional) After you select this option, CCE will automatically install Volcano Scheduler and set the default scheduler of the cluster to Volcano. This will enable you to access advanced scheduling capabilities for batch computing and high-performance computing.

Cloud Native Logging

(Optional) If selected, this add-on (Cloud Native Log Collection) will be automatically installed. Cloud Native Logging helps report logs to LTS. After the cluster is created, you are allowed to obtain and manage collection rules on the Logging page of the CCE cluster console.

CCE Node Problem Detector

(Optional) If selected, this add-on (CCE Node Problem Detector) will be automatically installed to detect faults and isolate nodes for prompt cluster troubleshooting.

CCE Container Network (Yangtse CNI)

This add-on is unconfigurable.

CCE Container Storage (Everest)

This add-on is unconfigurable. After the cluster is created, choose Add-ons in the navigation pane of the cluster console and modify the configuration.

CoreDNS

This add-on is unconfigurable. After the cluster is created, choose Add-ons in the navigation pane of the cluster console and modify the configuration.

NodeLocal DNSCache

This add-on is unconfigurable. After the cluster is created, choose Add-ons in the navigation pane of the cluster console and modify the configuration.

Cloud Native Logging

Select the logs to be collected. If enabled, a log group named k8s-log-{clusterId} will be automatically created, and a log stream will be created for each selected log type.

If log collection is disabled, choose Logging in the navigation pane of the cluster console after the cluster is created and enable this function.

CCE Node Problem Detector

This add-on is unconfigurable. After the cluster is created, choose Add-ons in the navigation pane of the cluster console and modify the configuration.