Buying a CCE Autopilot Cluster

Type

CCE Autopilot Cluster

CCE allows you to create various types of clusters for diverse needs.

• CCE standard clusters provide highly reliable and secure containers for commercial use.
• CCE Turbo clusters use high-performance cloud native networks and provide cloud native hybrid scheduling. Such clusters have improved resource utilization and can be used in more scenarios.
• CCE Autopilot clusters are serverless, and you do not need to bother with server O&M. This greatly reduces O&M costs and improves application reliability and scalability.

For more information about cluster types, see Cluster Comparison.

Cluster Name

autopilot-example

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

Enter 4 to 128 characters. Start with a lowercase letter and do not end with a hyphen (-). Only lowercase letters, digits, and hyphens (-) are allowed.

Enterprise Project

default

This parameter is only available for enterprise users who have enabled Enterprise Project Management Service (EPS).

After you select an enterprise project (for example, default), the cluster and resources in the cluster are created in the selected enterprise project. You can use enterprise projects to manage clusters and other resources (such as elastic load balancers and EVS disks). For more information, see Enterprise Management.

If there is no special requirement, you can select default.

Cluster Version

v1.31

Select the Kubernetes version used by the cluster. You are advised to select the latest version.

VPC

vpc-autopilot

Select a VPC where the cluster will be running. If no VPC is available, click Create VPC on the right to create one. For details, see Creating a VPC and Subnet. The VPC cannot be changed after the cluster is created.

Control Plane Subnet

subnet-502f

Select the subnet where the control plane is located. The cluster control plane node uses the IP address in this subnet by default. Ensure that the subnet has sufficient available IPv4 addresses. The subnet cannot be modified after being created.

If no subnet is available, click Create Subnet on the right to create one. For details, see Creating a VPC and Subnet.

Pod Subnet

subnet-502f

Select the subnet where the pods will be running. Each pod requires a unique IP address. The number of IP addresses in a subnet determines the maximum number of pods in a cluster and the maximum number of containers. After the cluster is created, you can add subnets.

If no subnet is available, click Create Subnet on the right to create one. For details, see Creating a VPC and Subnet.

Service CIDR Block

10.247.0.0/16

Select a Service CIDR block, which will be used by containers in the cluster to access each other. This CIDR block determines the maximum number of Services. After the cluster is created, the Service CIDR block cannot be changed.

VPC Endpoint (Image Access)

-

To ensure that your cluster nodes can pull images from SWR, existing SWR and OBS endpoints in the selected VPC are used by default. If there are no such endpoints, new SWR and OBS endpoints will be automatically created.

VPC endpoints are billed. For details, see VPC Endpoint Price Calculator.

Enable Alarm Center

If this option is selected, Alarm Center is automatically enabled for the cluster, and default alarm rules are created. For details about alarm rules, see Table 1.

Metric alarm rules rely on the Cloud Native Cluster Monitoring add-on to report data to AOM. If this add-on is not installed or connected to AOM, the alarm center will not create such alarm rules.

√

Contact Group

Select one or more contact groups to manage alarm notifications by group. After a contact group is selected, CCE automatically pushes alarms to the contact group based on alarm rules.

Alarm notifications are billed. For details, see Simple Message Notification Billing.

√

Alarm Center

Disabled

Alarm Center provides comprehensive cluster alarm capabilities so that alarms can be generated in a timely manner when faults occur during cluster running, ensuring service stability. If this option is enabled, the default alarm rules will be created, and notifications will be sent to the selected contact group. For details, see Configuring Alarms in Alarm Center.

SNAT

Disabled

This option is disabled by default, and the cluster can access the Internet through a NAT gateway. By default, an existing NAT gateway in the selected VPC is used. If there are no NAT gateways, CCE Autopilot automatically creates a NAT gateway with default specifications, binds an EIP to the NAT gateway, and configures SNAT rules.

The NAT gateway will be billed. For details, see NAT Gateway Billing.

Resource Tag

-

You can add resource tags to classify resources.

You can create predefined tags on the Tag Management Service (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. For details, see Creating Predefined Tags.

• A tag key can have a maximum of 128 characters and must not begin with _sys_. It can only contain letters, digits, spaces, and the following special characters: -_.:=+@. The key cannot be empty.
• A tag value can have a maximum of 255 characters. It can only contain letters, digits, spaces, and the following special characters: -_.:/=+@. The value can be empty.

Description

-

Enter a maximum of 200 characters except the following: ^~#$%&*<>()[]{}"'\.

CoreDNS

-

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

Kubernetes Metrics Server

-

This add-on is installed by default. It collects resource usage metrics, such as the container CPU and memory usages, for the cluster.

Cloud Native Cluster Monitoring

Select this add-on.

This is an optional add-on. If selected, this add-on (Cloud Native Cluster Monitoring) will be automatically installed. It collects monitoring metrics for your cluster and reports the metrics to Application Operations Management (AOM). The agent mode does not support HPA based on custom Prometheus statements. If related functions are required, install this add-on manually after the cluster is created.

If this add-on is selected, pod billing is involved. You can view the prices on the console.

Cloud Native Log Collection

Select this add-on.

This is an optional add-on. If selected, this add-on (Cloud Native Log Collection) will be automatically installed. Cloud Native Log Collection 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.

LTS does not charge you for creating log groups and offers a free quota for log collection every month. You pay only for log volume that exceeds the quota. For details, see Price Calculator. For details, see Collecting Logs.

If this add-on is selected, pod billing is involved. You can view the prices on the console.