Pay-per-Use Billing
Pay-per-use is a postpaid billing mode. If you expect to use resources flexibly, this billing mode is suitable. This section describes the billing rules for pay-per-use CCE Autopilot resources.
Application Scenarios
Pay-per-use billing is good for short-term, bursty, or unpredictable workloads, such as applications for e-commerce promotions, temporary testing, and scientific computing.
Billed Items
When creating a CCE Autopilot cluster, you can select pay-per-use billing from the CCE console for the billed items in Table 1. By default, other cloud service resources automatically created on the CCE console are billed on a pay-per-use basis based on their standard pricing.
|
Billed items |
Description |
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. |
Unit price of cluster management × Required duration For details about the unit prices of cluster management, see Unit Prices in Pay-per-Use Billing. |
|
*Pods |
The expenditures for vCPUs, memory, and storage.
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. By default, 30-GiB 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 30 GiB will be billed separately. |
Unit price of the pod specification × Required duration For details about the 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 are using. |
Unit price of the VPC endpoint × Required duration For details about the unit prices of VPC endpoint specifications, see VPC Endpoint Price Calculator. NOTE:
See the pricing on the VPC Endpoint console. |
Billed Usage Period
A pay-per-use CCE resource is calculated by the second but billed every hour (GMT+08:00). Once settlement is complete, it enters a new billed usage period. The billing starts when a cluster or pod is created and ends when the cluster or pod is deleted.
NOTE:
It takes a certain time to launch a CCE cluster or pod, so the billing starts from the time when the cluster or pod is successfully created.
To view the cluster creation time, access Operation Records on the CCE console.
To view the pod creation time, click the cluster name to go to the cluster overview page on the CCE console. In the navigation pane, choose Workloads. On the right of the page, click the corresponding workload tab and then the workload name. On the Pods tab, view the pod creation time in the Created column.
For example, if you purchased a pay-per-use cluster at 08:45:30 and deleted it at 08:55:30, you are billed for the 600 seconds from 08:45:30 to 08:55:30.
For example, if you purchased a pay-per-use pod at 8:48:30 and deleted it at 8:50:30, you are billed for the 120 seconds from 8:48:30 to 8:50:30.
Impacts of Arrears
Figure 1 shows the statuses a pay-per-use resource can have throughout its lifecycle. After a resource is purchased, it enters the valid period and runs normally during this period. If your account goes into arrears, the resource enters a grace period and then a retention period.
Arrears Reminder
You will be billed for the pay-per-use resource after each billed usage period ends. If your account goes into arrears, we will notify you by email, SMS, or in-app message.
Impacts of Arrears
If your account is insufficient to pay your amount due, your account goes into arrears, and the resource enters the grace period. You are still responsible for expenditures generated during the grace period. You can view the charges on the Overview page in Billing Center and pay any past due balance as needed.
If you do not bring your account current before the grace period expires, the resource turns to Frozen and enters a retention period. You cannot perform any operations on a pay-per-use resource in the Frozen state.
If you do not bring your account current before the retention period ends, CCE Autopilot clusters and resources like pods and EIPs will be released and cannot be restored.
NOTE:
- Once a yearly/monthly subscription has expired or a pay-per-use resource becomes in arrears, Huawei Cloud provides a period of time during which you can renew or top up your accounts. For details, see What Is a Grace Period of Huawei Cloud? How Long Is It? What Is a Retention Period of Huawei Cloud? How Long Is It?
- For details about top-up, see Topping Up an Account.
Unit Prices in Pay-per-Use Billing
NOTICE:
By default, 30 GiB of ephemeral storage is allocated to each pod for free (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 |
Pod |
|---|---|---|
|
AP-Singapore |
$0.1 USD/hour |
|
|
AP-Bangkok |
$0.1 USD/hour |
|
|
AP-Jakarta |
$0.1 USD/hour |
|
|
AF-Johannesburg |
$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 |
|
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
