Help Center/ Cloud Container Engine_Autopilot/ User Guide/ Clusters/ Buying a CCE Autopilot Cluster
Updated on 2024-11-08 GMT+08:00
View PDF
Share

Buying a CCE Autopilot Cluster

A CCE Autopilot cluster runs on Cloud Container Instance (CCI) and provides native Kubernetes extended APIs, allowing you to run containers without creating or managing servers. You pay only for the resources used by your applications.

Constraints

  • After a cluster is created, the following items cannot be changed:
    • Cluster type
    • Network configuration of the cluster, such as the VPC, pod subnet, Service CIDR block, and kube-proxy (request forwarding) settings.
  • When using a CCE Autopilot cluster, pay attention to the quotas of related resources. The following table lists the resources required by each cluster.

    Service

    Quota Item

    Minimum Usage

    Minimum Usage

    Region Limits

    Quota Increase

    CCE

    Cluster

    1

    -

    Maximum number of clusters that can be created by each account in a region: 50

    Increase the quota on the My Quotas page.

    VPC

    VPC

    1 per cluster

    Select one VPC for each cluster to provide an isolated, private virtual network environment for the cluster.

    Maximum number of VPCs that can be created by each account in a region: 5

    Subnet

    1 per cluster

    At least one subnet must be selected for each cluster to allocate container IP addresses.

    By default, the cluster control plane occupies eight IP addresses for control plane deployment and interconnection with external services.

    Maximum number of subnets that can be created by each account in a region: 50

    Security group

    2 per cluster

    Two security groups are automatically created for each cluster for network access control of the cluster control plane and elastic network interfaces.

    Maximum number of security groups that can be created by each account in a region: 100

    Security group rules

    7 per cluster

    Seven security group rules are automatically added for each cluster to allow traffic over specified ports and ensure normal network communication in the cluster.

    Maximum number of security groups rules that can be added by each account in a region: 1,000

    VPC Endpoint

    Endpoint

    3 per cluster

    Reserve at least three endpoints for each cluster so that the cluster can access peripheral services such as SWR and OBS.

    Maximum number of VPC endpoints that can be created by each account in a region: 50

    Domain Name Service (DNS)

    Private zone

    2 per cluster

    Each cluster requires at least two private domain names for normal communication within the cluster or across clusters.

    Maximum number of private zones that can be created by each account in a region: 50

    Record set

    6 per cluster

    Each cluster requires at least six DNS record sets for mapping specified domain names to IP addresses or other domain names in the cluster.

    Maximum number of record sets that can be added by each account in a region: 500

Step 1: Log In to the CCE Console

  1. Log in to the CCE console.
  2. On the Clusters page, click Buy Cluster in the upper right corner.

Step 2: Configure the Cluster

On the Buy Cluster page, configure the parameters.

Basic Settings

Parameter

Description

Type

Select CCE Autopilot cluster.

Cluster Name

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

Enterprise Project

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

Enterprise projects facilitate project-level management and grouping of cloud resources and users. For more information, see Enterprise Management.

After you select an enterprise project (for example, default), the cluster and resources in the cluster are created in the selected enterprise project. For easier resource management, do not change the enterprise project after the cluster is created.

Cluster Version

Select the Kubernetes version used by the cluster.

Network Settings

Parameter

Description

VPC

Select the VPC that the cluster belongs to. If no VPC is available, create one first. Once a cluster is created, the VPC cannot be changed.

Pod Subnet

Select the subnet that the pods belong to. If no subnet is available, create one first. This subnet determines how many pods you can create in a cluster. After the cluster is created, you can add more subnets.

Service CIDR Block

Configure the Service CIDR block for containers in the same cluster to access each other. The CIDR block determines how many Services you can create. Once a cluster is created, the Service CIDR block cannot be changed.

Image Access

To ensure that the nodes in a cluster can pull images from SoftWare Repository for Container (SWR), existing endpoints in the selected VPC are used by default. If there are no endpoints in the VPC, new endpoints will be created for you to access SWR and OBS.

VPC endpoints are not free. For details, see VPC Endpoint Pricing.

SNAT

If this option is enabled, a cluster can access the Internet through a NAT gateway. By default, an existing NAT gateway in the selected VPC is used. If there is no NAT gateway in the VPC, a new NAT gateway of the default specifications will be created, with an SNAT rule added and an EIP specified in the rule.

NAT gateways are not free. For details, see NAT Gateway Pricing.

(Optional) Advanced Settings

Parameter

Description

Alarm Center

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.

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 no more than 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

You can enter up to 200 characters.

Step 3: Select Add-ons

Click Next: Select Add-on. On the page displayed, select the add-ons to be installed during cluster creation.

Basic capabilities

Add-on

Description

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.
Observability

Add-on

Description

Kubernetes Metrics Server

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

Cloud Native Cluster Monitoring

(Optional) 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.

Cloud Native Logging

(Optional) If selected, this add-on (Cloud Native Logging) 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.

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.

Step 4: Configure Add-ons

Click Next: Add-on Configuration. The add-ons that are installed by default cannot be configured. After the cluster is created, you can go to the Add-ons page to modify their settings.

The table describes how to configure the optional add-ons.

Observability

Add-on

Description

Cloud Native Cluster Monitoring

Select an AOM instance for the add-on to report metrics. If no AOM instance is available, create one first.

Basic metrics are free, but custom metrics are billed based on the standard pricing of AOM. For details, see AOM Pricing Details.

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.

  • Container log: Standard output logs of containers are collected. The corresponding log stream is named in the format of stdout-{Cluster ID}.
  • Kubernetes Events: Kubernetes logs are collected. The corresponding log stream is named in the format of event-{Cluster ID}.

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

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.

Step 5: Confirm the Configuration

Click Next: Confirm configuration. The cluster resource list is displayed. Confirm the information and click Submit.

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

Related Operations

Parent Topic: Clusters