Easily Switch Between Product Types
You can click the drop-down list box to switch between different product types.
- Function Overview
- Product Bulletin
- Service Overview
- Billing
- Getting Started
-
User Guide
- Clusters
- Workloads
- Network
- Storage
- O&M
- Namespaces
- ConfigMaps and Secrets
- Auto Scaling
- Add-ons
- Helm Chart
- Permissions
- Settings
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs
- Autopilot Cluster Management
- Add-on Management for Autopilot Clusters
-
Autopilot Cluster Upgrade
- Upgrading a Cluster
- Obtaining Cluster Upgrade Task Details
- Retrying a Cluster Upgrade Task
- Obtaining a List of Cluster Upgrade Task Details
- Performing a Pre-upgrade Check for a Cluster
- Obtaining Details About a Pre-upgrade Check Task of a Cluster
- Obtaining a List of Pre-upgrade Check Tasks of a Cluster
- Performing a Post-upgrade Check for a Cluster
- Backing Up a Cluster
- Obtaining a List of Cluster Backup Task Details
- Obtaining the Cluster Upgrade Information
- Obtaining a Cluster Upgrade Path
- Obtaining the Configuration of Cluster Upgrade Feature Gates
- Enabling the Cluster Upgrade Process Booting Task
- Obtaining a List of Upgrade Workflows
- Obtaining Details About a Specified Cluster Upgrade Booting Task
- Updating the Status of a Specified Cluster Upgrade Booting Task
- Quota Management for Autopilot Clusters
- Tag Management for Autopilot Clusters
-
Chart Management for Autopilot Clusters
- Uploading a Chart
- Obtaining a Chart List
- Obtaining a Release List
- Creating a Release
- Updating a Chart
- Deleting a Chart
- Updating a Release
- Obtaining a Chart
- Deleting a Release
- Obtaining a Release
- Downloading a Chart
- Obtaining Chart Values
- Obtaining Historical Records of a Release
- Obtaining the Quota of a User Chart
- Kubernetes APIs
- Permissions and Supported Actions
- Appendix
-
FAQs
- Billing
- Workloads
- Network Management
-
Storage
- Can PVs of the EVS Type in a CCE Autopilot Cluster Be Restored After They Are Deleted or Expire?
- What Can I Do If a Storage Volume Fails to Be Created?
- Can CCE Autopilot PVCs Detect Underlying Storage Faults?
- How Can I Delete the Underlying Storage If It Remains After a Dynamically Created PVC is Deleted?
- Permissions
- General Reference
Copied.
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).
NOTE:
The billed items marked with asterisks (*) are mandatory.
|
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 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 use. |
Pay-per-use |
Unit price of the VPC endpoint x Required duration NOTE:
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
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
