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 billing items marked with asterisks (*) are mandatory.
|
Billing Item |
Description |
Billing Mode |
Formula |
|---|---|---|---|
|
*Cluster management |
The expenditures 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 |
Billed based on the vCPU, memory, and temporary storage specifications.
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 and packages (CPU and/or memory packages) |
Unit price of the pod specification x Required duration For details about the unit prices, see Unit Prices in Pay-per-Use Billing. |
|
*VPC endpoints |
CCE Autopilot clusters access other cloud services such as SWR through VPC endpoints. Each VPC endpoint is billed based on the usage duration. |
Pay-per-use |
Unit price of the VPC endpoint x Required duration
NOTE:
See the pricing on the VPC Endpoint console. |
|
Other cloud resources |
Cloud service resources used by a cluster such as an elastic load balancer are billed based on their pricing rules, no matter whether these resources are automatically or manually created when the cluster is being created and used. Although cloud service resources can be created on the CCE console, their billing 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
By default, 30 GiB of free ephemeral storage is allocated to each pod (with an IOPS upper limit of 2,500 and a burst limit of 16,000). Any storage space that exceeds the 30 GiB quota will be billed separately.
|
Region |
Cluster Management |
Pods |
|---|---|---|
|
AP-Singapore |
$0.1 USD/hour |
|
|
AP-Bangkok |
$0.1 USD/hour |
|
|
AP-Jakarta |
$0.1 USD/hour |
|
|
AF-Johannesburg |
$0.1 USD/hour |
|
|
TR-Istanbul |
$0.1 USD/hour |
|
|
ME-Riyadh |
$0.1 USD/hour |
|
|
LA-Sao Paulo1 |
$0.1 USD/hour |
|
|
CN-Hong Kong |
$0.1 USD/hour |
|
|
CN Southwest-Guiyang1 |
$0.1 USD/hour |
|
|
CN South-Guangzhou |
$0.1 USD/hour |
|
|
CN East-Shanghai1 |
$0.1 USD/hour |
|
|
CN North-Beijing4 |
$0.1 USD/hour |
|
|
CN North-Ulanqab1 |
$0.1 USD/hour |
|
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.
|
vCPU |
Memory (GiB) |
|---|---|
|
0.25 vCPUs |
0.5, 1, and 2 |
|
0.5 vCPUs |
1, 2, 3, and 4 |
|
1 vCPU |
2 to 8 (increment: 1 GiB) |
|
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 |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
