- 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
Show all
Copied.
Billing Mode Overview
CCE Autopilot supports two billing modes: pay-per-use and packages.
- Pay-per-use: You can start using CCE Autopilot resources first and then pay as you go. Their usage durations are calculated by the second but billed every hour. This allows you to flexibly adjust the resources. You neither need to prepare for resources in advance, nor end up with excessive or insufficient preset resources. Pay-per-use billing is a good option for scenarios where there are sudden traffic bursts, such as e-commerce promotions. For details about pay-per-use billing, see Pay-per-Use Billing.
- Package: You need to pay for packages before using them. Their usages are settled every hour. Packages are suitable for services with stable demand for a long time. You can buy more packages to enjoy more discounts. For details about packages, see Package Overview.
NOTE:
On the Overview page of the cluster console, you can purchase CPU and/or memory packages required by pods by referring to Buying a Package. After you purchase a package in a region, it can be used by all pods in all CCE Autopilot clusters in that region.
In addition to the vCPU and memory required by pods, no packages are provided for the cluster management, VPC endpoints, and ephemeral storage (the part in excess of 30 GiB) required by pods. Also, packages are unavailable for other cloud service resources on the CCE console. When a cloud service resource is created on the CCE console, it is billed on a pay-per-use basis by default. You can go to the corresponding cloud service console to purchase yearly/monthly cloud service resources or packages. These resources or packages will be billed based on their standard prices.
Billing Mode |
Package |
|
---|---|---|
Payment |
Postpaid. You are billed based on the actual usage durations. |
Prepaid. The packages are used first during the subscription period. |
Billed Usage Period |
Calculated by the second but billed every hour |
Billed based on the purchase period in the order. For details, see Package Billing Cycle. |
Billed Items |
All billed items |
Only CPU and memory required by the pods |
Application Scenarios |
Recommended when the resource demands are likely to fluctuate and you want more flexibility |
A cost-effective option for scenarios where the resource usage duration is predictable. It is recommended for resources expected to be used for a long term. |
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