- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
- User Guide
- Best Practices
-
Developer Guide
- Overview
- Using Native kubectl (Recommended)
- Namespace and Network
- Pod
- Label
- Deployment
- EIPPool
- EIP
- Pod Resource Monitoring Metric
- Collecting Pod Logs
- Managing Network Access Through Service and Ingress
- Using PersistentVolumeClaim to Apply for Persistent Storage
- ConfigMap and Secret
- Creating a Workload Using Job and Cron Job
- YAML Syntax
-
API Reference
- Before You Start
- Calling APIs
- Getting Started
- Proprietary APIs
-
Kubernetes APIs
- ConfigMap
- Pod
- StorageClass
- Service
-
Deployment
- Querying All Deployments
- Deleting All Deployments in a Namespace
- Querying Deployments in a Namespace
- Creating a Deployment
- Deleting a Deployment
- Querying a Deployment
- Updating a Deployment
- Replacing a Deployment
- Querying the Scaling Operation of a Specified Deployment
- Updating the Scaling Operation of a Specified Deployment
- Replacing the Scaling Operation of a Specified Deployment
- Querying the Status of a Deployment
- Ingress
- OpenAPIv2
- VolcanoJob
- Namespace
- ClusterRole
- Secret
- Endpoint
- ResourceQuota
- CronJob
-
API groups
- Querying API Versions
- Querying All APIs of v1
- Querying an APIGroupList
- Querying APIGroup (/apis/apps)
- Querying APIs of apps/v1
- Querying an APIGroup (/apis/batch)
- Querying an APIGroup (/apis/batch.volcano.sh)
- Querying All APIs of batch.volcano.sh/v1alpha1
- Querying All APIs of batch/v1
- Querying All APIs of batch/v1beta1
- Querying an APIGroup (/apis/crd.yangtse.cni)
- Querying All APIs of crd.yangtse.cni/v1
- Querying an APIGroup (/apis/extensions)
- Querying All APIs of extensions/v1beta1
- Querying an APIGroup (/apis/metrics.k8s.io)
- Querying All APIs of metrics.k8s.io/v1beta1
- Querying an APIGroup (/apis/networking.cci.io)
- Querying All APIs of networking.cci.io/v1beta1
- Querying an APIGroup (/apis/rbac.authorization.k8s.io)
- Querying All APIs of rbac.authorization.k8s.io/v1
- Event
- PersistentVolumeClaim
- RoleBinding
- StatefulSet
- Job
- ReplicaSet
- Data Structure
- Permissions Policies and Supported Actions
- Appendix
- Out-of-Date APIs
- Change History
-
FAQs
- Product Consulting
-
Basic Concept FAQs
- What Is CCI?
- What Are the Differences Between Cloud Container Instance and Cloud Container Engine?
- What Is an Environment Variable?
- What Is a Service?
- What Is Mcore?
- What Are the Relationships Between Images, Containers, and Workloads?
- What Are Kata Containers?
- Can kubectl Be Used to Manage Container Instances?
- What Are Core-Hours in CCI Resource Packages?
- Workload Abnormalities
-
Container Workload FAQs
- Why Service Performance Does Not Meet the Expectation?
- How Do I Set the Quantity of Instances (Pods)?
- How Do I Check My Resource Quotas?
- How Do I Set Probes for a Workload?
- How Do I Configure an Auto Scaling Policy?
- What Do I Do If the Workload Created from the sample Image Fails to Run?
- How Do I View Pods After I Call the API to Delete a Deployment?
- Why an Error Is Reported When a GPU-Related Operation Is Performed on the Container Entered by Using exec?
- Can I Start a Container in Privileged Mode When Running the systemctl Command in a Container in a CCI Cluster?
- Why Does the Intel oneAPI Toolkit Fail to Run VASP Tasks Occasionally?
- Why Are Pods Evicted?
- Why Is the Workload Web-Terminal Not Displayed on the Console?
- Why Are Fees Continuously Deducted After I Delete a Workload?
-
Image Repository FAQs
- Can I Export Public Images?
- How Do I Create a Container Image?
- How Do I Upload Images?
- Does CCI Provide Base Container Images for Download?
- Does CCI Administrator Have the Permission to Upload Image Packages?
- What Permissions Are Required for Uploading Image Packages for CCI?
- What Do I Do If Authentication Is Required During Image Push?
-
Network Management FAQs
- How Do I View the VPC CIDR Block?
- Does CCI Support Load Balancing?
- How Do I Configure the DNS Service on CCI?
- Does CCI Support InfiniBand (IB) Networks?
- How Do I Access a Container from a Public Network?
- How Do I Access a Public Network from a Container?
- What Do I Do If Access to a Workload from a Public Network Fails?
- What Do I Do If Error 504 Is Reported When I Access a Workload?
- What Do I Do If the Connection Timed Out?
- Storage Management FAQs
- Log Collection
- Account
- SDK Reference
- Videos
- General Reference
Copied.
Pay-per-Use Billing
Overview
Pay-per-use billing means you pay nothing up front and are not tied into any contract or commitment.
Application Scenarios
Pay-per-use billing is good for short-term, bursty, or unpredictable workloads that cannot tolerate any interruptions, such as applications for e-commerce flash sales, temporary testing, and scientific computing.
Billed Items
You are billed for pods on a pay-per-use basis.
Billed Item |
Description |
---|---|
General-computing pods |
vCPUs and memory are billed on a pay-per-use basis. |
Assume that you plan to purchase a general-computing pod. At the bottom of the page for you to purchase a pod, you can view price details.

The price covers the vCPUs and memory.
Billed Usage Period
The usage of pay-per-use pods is calculated by the second but billed every hour. Billing starts when a pod is created and ends when the pod is deleted.
For example, if you purchased a general-computing pod at 08:45:30 and deleted it at 08:55:30, you are billed for the 600 seconds from 8:45:30 to 8:55:30.
Billing Example
Assume that you purchased a pay-per-use general-computing pod (2 vCPUs and 4 GiB of memory) at 9:59:30 on April 18, 2023 and deleted it at 10:45:46 on April 18, 2023. Two usage periods are billed:
- 9:59:30 to 10:00:00: 30 seconds
- 10:00:00 to 10:45:46: 2,746 seconds
You need to pay for each period. Table 2 describes how vCPUs and memory are billed.
Item |
Formula |
Unit Price |
---|---|---|
vCPU |
Unit price x Number of vCPUs x Required duration |
For details, see CCI Pricing Details. |
Memory |
Unit price x Memory size x Required duration |
For details, see CCI Pricing Details. |
Impact on Billing After Specifications Change
If you change the specifications of a pay-per-use pod, the original order will become invalid and a new order will be placed. You will be billed based on the new specifications.
If you change specifications within a given hour, multiple records will be generated. Different bills record the billing for different specifications.
For example, if you purchased a pay-per-use pod with 2 vCPUs and 4 GiB of memory at 9:00:00 and upgraded the pod to 4 vCPUs and 8 GiB of memory at 9:30:00, the following items will be billed:
- Usage of 2 vCPUs and 4 GB of memory from 9:00:00 to 9:30:00
- Usage of 4 vCPUs and 8 GiB of memory from 9:30:00 to 10:00:00
Impacts of Arrears
Figure 2 shows the statuses that a pay-per-use pod can have throughout its lifecycle. After a pod is purchased, it enters the valid period and runs normally during this period. If your account goes into arrears, the pod enters a grace period and then a retention period.
Arrears Alert
The system will bill you for pay-per-use pods after each billing cycle 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. Pay-per-use pods are not stopped immediately. You are still responsible for expenditures generated during the grace period. You can view the charges on the Billing Center > Overview page and pay any past due balance as needed.
If you do not pay the arrears within the grace period, your resources will enter the retention period and become frozen. You cannot perform any operations on the pay-per-use resources during this period.
If you do not bring your account balance current before the retention period ends, the compute resources (vCPUs and memory) will be released and data cannot be restored.
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