Buying a CCE Cluster

Constraints

• During the node creation, software packages are downloaded from OBS using the domain name. A private DNS server must be used to resolve the OBS domain name. Therefore, the DNS server address of the subnet where the node resides must be set to the private DNS server address so that the node can access the private DNS server. When you create a subnet, the private DNS server is used by default. If you change the subnet DNS, ensure that the DNS server in use can resolve the OBS domain name.
• You can create a maximum of 50 clusters in a single region.
• After a cluster is created, the following items cannot be changed:
  • Cluster type
  • Number of master nodes in the cluster
  • AZ of a master node
  • Network configurations of the cluster, such as the VPC, subnet, container CIDR block, Service CIDR block, and kube-proxy settings.
  • Network model. For example, change Tunnel network to VPC network.

Procedure

1. Log in to the CCE console.
2. In the upper right corner of the Clusters page, click Buy Cluster and select the type of the cluster to be created.
3. Specify cluster parameters.

   Basic Settings

   Parameter	Description
   Billing Mode	Select a billing mode for the cluster as required. Pay-per-use: a postpaid billing mode. It is suitable in scenarios where resources will be billed based on usage frequency and duration. You can provision or delete resources at any time.
   Cluster Name	Enter a cluster name. Cluster names under the same account must be unique.
   Enterprise Project	This parameter is displayed only for enterprise users who have enabled the enterprise project function. After an enterprise project (for example, default) is selected, the cluster, nodes in the cluster, cluster security groups, node security groups, and elastic IPs (EIPs) of the automatically created nodes will be created in this enterprise project. After the cluster is created, do not modify the enterprise projects of nodes, cluster security groups, and node security groups in the cluster. Enterprise projects facilitate project-level management and grouping of cloud resources and users.
   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.
   HA	Select the distribution mode of master nodes. By default, master nodes are randomly distributed in different AZs to improve DR. You can also expand advanced settings and customize the master node distribution mode. The following modes are supported: Random: Master nodes are deployed in different AZs for DR. Custom: Master nodes are deployed in specific AZs. Host: Master nodes are deployed on different hosts in the same AZ for cluster DR. Custom: Master nodes are deployed in the AZs you specified.

   Network Settings

   The network settings cover nodes, containers, and Services. For details about the cluster networking and container network models, see Overview.

   Parameter	Description
   Network Model	Select VPC network or Tunnel networkfor your CCE standard cluster. Select Cloud Native Network 2.0 for your CCE Turbo cluster. For more information about their differences, see Overview.
   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 being specified.
   Master Node Subnet	Select the subnet where the control plane (master nodes in the cluster) is located. If no subnet is available, click Create Subnet to create one. The subnet cannot be changed after creation.
   Container CIDR Block (configured for CCE standard clusters)	Configure the CIDR block used by containers. The value determines the maximum number of containers in your cluster.
   Default Pod Subnet (configured for CCE Turbo clusters)	Select the subnet to which the pod belongs. If no subnet is available, click Create Subnet to create one. The pod subnet determines the maximum number of containers in a cluster. You can add pod subnets after a cluster is created.
   IPv4 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. This configuration cannot be modified after the cluster is created.

   Advanced Settings

   Parameter	Description
   Request Forwarding	Select IPVS or iptables for your cluster. For details, see Comparing iptables and IPVS. iptables is the traditional kube-proxy mode. This mode applies to the scenario where the number of Services is small or a large number of short connections are concurrently sent on the client. IPVS allows higher throughput and faster forwarding. This mode applies to scenarios where the cluster scale is large or the number of Services is large.
   CPU Manager	If enabled, exclusive CPU cores can be allocated to workload pods. For details, see CPU Policy.
   Resource Tag	You can add resource tags to classify resources. You can create predefined tags on the TMS console. The predefined tags are available to all resources that support tags. You can use predefined tags to improve the tag creation and resource migration efficiency. Key Specifications Cannot be empty. Contains 1 to 128 single-byte characters. Do not enter labels starting with _sys_, which are system labels. Can contain UTF-8 letters, digits, spaces, and the following characters: _. : / = + - @ Recommended regular expression: ^((?!_sys_)[\\p{L}\\p{Z}\\p{N}_.:\\/=+\\-@]*)$ Value Specifications Can contain up to 255 characters. Can contain UTF-8 letters, digits, spaces, and the following characters: _. : / = + - @ Recommended regular expression: ^([\p{L}\p{Z}\p{N}_.:\/=+\-@]*)$ The value can be empty or null. The value of a predefined tag cannot be empty or null.
   Default Node Security Group	Select the security group automatically generated by CCE or use the existing one as the default security group of the node. NOTICE: The default node security group needs to allow access from certain ports to ensure normal communication. Otherwise, the node cannot be created..
   Certificate Authentication	Default: The X509-based authentication mode is enabled by default. X509 is a commonly used certificate format. Custom: The cluster can identify users based on the header in the request body for authentication. Upload your CA root certificate, client certificate, and private key of the client certificate. CAUTION: Upload a file smaller than 1 MB. The CA certificate and client certificate can be in .crt or .cer format. The private key of the client certificate can only be uploaded unencrypted. The validity period of the client certificate must be longer than five years. The uploaded CA root certificate is used by the authentication proxy and for configuring the kube-apiserver aggregation layer. If any of the uploaded certificates is invalid, the cluster cannot be created. Starting from v1.25, Kubernetes no longer supports certificate authentication generated using the SHA1WithRSA or ECDSAWithSHA1 algorithm. The certificate authentication generated using the SHA256 algorithm is supported instead.
   Description	Enter 1 to 200 characters.

4. Click Next: Configure Add-on.

   Parameter	Description
   Domain Name Resolution	The coredns add-on is installed by default to resolve domain names and connect to the cloud DNS server. The node-local-dns add-on is automatically installed to improve cluster DNS performance by running the DNS cache proxies on cluster nodes.
   Container Storage	The automatically installed everest add-on provides CSI-backed container storage and connects to in-cloud storage services such as EVS.
   Fault Detection	The npd add-on is installed by default to detect faults and isolate nodes for prompt cluster troubleshooting.
   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 Cluster Overload Control.

5. After the parameters are specified, click Next: Confirm. The cluster resource list is displayed. Confirm the information and click Submit.

   It takes about 6 to 10 minutes to create a cluster. You can click Back to Cluster List to perform other operations on the cluster or click Go to Cluster Events to view the cluster details.

Related Operations

• After creating a cluster, you can use the Kubernetes command line (CLI) tool kubectl to connect to the cluster. For details, see Connecting to a Cluster Using kubectl.
• Add nodes to the cluster. For details, see Creating a Node.