Updated on 2024-07-05 GMT+08:00

CCE Autopilot Cluster Billing

The price of a CCE Autopilot cluster consists of the following parts: cluster management, pods, and cloud resources (VPC endpoints and other cloud resources).

The billed items marked with asterisks (*) are mandatory.

Table 1 Price of a CCE Autopilot cluster

Billed Item

Description

Billing Mode

Formula

*Cluster management

The expenses for managing the cluster

NOTE:

If a cluster is frozen, workloads in the cluster will be in the pending state and will not be rescheduled until the cluster is unfrozen.

Pay-per-use

Unit price of the cluster specification x Required duration

For details about the unit prices of cluster specifications, see Unit Prices in Pay-per-Use Billing.

*Pods

Pods are billed by specification.

NOTICE:

If a specification is not supported, it will be automatically upgraded to a higher one. For example, if all containers in a pod require 2 vCPUs and 3 GiB of memory, the specification is automatically upgraded to 2 vCPUs and 4 GiB of memory. Specification Description lists the specifications supported by CCE Autopilot.

Pay-per-use

Unit price of the pod specification x Required duration

For details about unit prices of pod specifications, see Unit Prices in Pay-per-Use Billing.

*VPC endpoints

CCE Autopilot clusters connect to other cloud services such as SWR through VPC endpoints, which are billed separately based on the number of VPC endpoints you use.

Pay-per-use

Unit price of the VPC endpoint x Required duration

NOTE:
  • If a VPC endpoint connects to a VPC endpoint service other than DNS or OBS, you will be billed for how long you use this VPC endpoint.
  • If a VPC endpoint connects to DNS or OBS, you will not be billed for this VPC endpoint.

See the pricing on the VPC Endpoint console.

Other cloud resources

Resources of cloud services used by a cluster such as Elastic Load Balance (ELB) are billed based on their pricing rules, no matter whether these resources are automatically created or manually added during cluster creation and use.

Although cloud resources can be created on the CCE console, their billed items and bills are independent of those of CCE clusters.

Billing mode of each cloud service

For details, see Price Calculator.

Unit Prices in Pay-per-Use Billing

Table 2 Unit prices in pay-per-use billing

Region

Cluster Management

Pod

AP-Singapore

Cluster management is free of charge during the OBT.

  • CPU: $0.0000126 USD/s per core
  • Memory: $0.00000138 USD/s per GiB

Specification Description

CCE Autopilot automatically upgrades the specifications that are not supported to higher ones to ensure that the pods always have the required resources.

Table 3 Combinations of vCPUs and memory supported by CCE Autopilot

vCPU

Memory (GiB)

0.25 vCPUs

0.5, 1, and 2

0.5 vCPUs

1, 2, 3, and 4

1 vCPU

2, 3, 4, 5, 6, 7, and 8

2 vCPUs

4 to 16 (increment: 1 GiB)

4 vCPUs

8 to 32 (increment: 1 GiB)

8 vCPUs

8 to 64 (increment: 4 GiB)

16 vCPUs

16 to 128 (increment: 8 GiB)

32 vCPUs

32, 64, 128, and 256

48 vCPUs

96, 192, and 384

64 vCPUs

128, 256, and 512