- What's New
- Product Bulletin
- Service Overview
- Billing
- Getting Started
-
User Guide
- Application Service Mesh
- Buying a Service Mesh
- Mesh Management
- Service Management
- Gateway Management
- Grayscale Release
- Mesh Configuration
- Traffic Management
- Security
-
Best Practices
- Upgrading Data Plane Sidecars Without Service Interruption
- Service Governance for Dubbo-based Applications
- Reserving Source IP Address for Gateway Access
- Creating a Service Mesh with IPv4/IPv6 Dual Stack Enabled
- How Do I Query Application Metrics in AOM?
- Reducing the Agency Permissions of ASM Users
- Istio-ingressgateway HA Configuration
-
FAQs
- Service Mesh Cluster
-
Mesh Management
- Why Cannot I Create a Mesh for My Cluster?
- Why Are Exclusive Nodes Still Exist After Istio Is Uninstalled?
- How Do I Upgrade ICAgent?
- How Do I Enable Namespace Injection for a Cluster?
- How Do I Disable Sidecar Injection for Workloads?
- What Can I Do If A Pod Cannot Be Started Due to Unready Sidecar
- How Do I Handle a Canary Upgrade Failure?
-
Adding a Service
- What Do I Do If an Added Gateway Does Not Take Effect?
- Why Does It Take a Long Time to Start the Demo Application in Experiencing Service Mesh in One Click?
- Why Cannot I Access the page of the Demo Application After It Is Successfully Deployed?
- Why Cannot I Select the Corresponding Service When Adding a Route?
- How Do I Inject a Sidecar for the Pod Created Using a Job or CronJob?
- Performing Grayscale Release
-
Managing Traffic
- Why Are the Created Clusters, Namespaces, and Applications Not Displayed on the Traffic Management Page?
- How Do I Change the Resource Requests of the istio-proxy Container?
- Does ASM Support HTTP/1.0?
- How Can I Block Access from Some IP Address Ranges or Ports for a Service Mesh?
- How Do I Configure max_concurrent_streams for a Gateway?
- How Do I Fix Compatibility Issues Between Istio CNI and Init Containers?
-
Monitoring Traffic
- Why Cannot I View Traffic Monitoring Data Immediately After a Pod Is Started?
- Why Are the Latency Statistics on the Dashboard Page Inaccurate?
- Why Is the Traffic Ratio Inconsistent with That in the Traffic Monitoring Chart?
- Why Can't I Find Certain Error Requests in Tracing?
- Why Cannot I Find My Service in the Traffic Monitoring Topology?
- How Do I Connect a Service Mesh to Jaeger or Zipkin for Viewing Traces?
- Videos
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Getting Started
- User Guide
-
FAQs
- Service Mesh Cluster
- Mesh Management
-
Adding a Service
- What Do I Do If an Added Gateway Does Not Take Effect?
- Why Does It Take a Long Time to Start the Demo Application in Experiencing Service Mesh in One Click?
- Why Cannot I Access the page of the Demo Application After It Is Successfully Deployed?
- Why Cannot I Select the Corresponding Service When Adding a Route?
- Performing Grayscale Release
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Copied.
Pay-per-Use Billing
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
Service mesh scale (maximum number of pods managed by a service mesh)
Billed Usage Period
The usage of pay-per-use resources is calculated by the second but billed every hour. The billing starts when a service mesh is created and ends when the service mesh is deleted.
- You will be billed for a pay-per-use service mesh of the Enterprise edition immediately after you purchase it. It takes some time to create a service mesh. The billing starts from the time when the service mesh was successfully created.
- A pay-per-use service mesh of the Enterprise edition that manages 20 pods or less is billed for 20 pods. If the service mesh manages more than 20 pods, it is billed according to the actual number of managed pods.
For example, if you purchased a pay-per-use service mesh at 8:45:30 and deleted it at 8:55:30, you are billed for the 600 seconds from 8:45:30 to 8:55:30.
Impact of Arrears
Figure 1 shows the statuses a pay-per-use service mesh can have throughout its lifecycle. After a service mesh is purchased, it enters the valid period and runs normally during this period. If your account goes into arrears, the service mesh enters a grace period and then a retention period.
Arrears Reminder
The system will bill you for pay-per-use resources after each billing cycle ends. If your account goes into arrears, we will notify you by email, SMS, or in-app message.
Impact of Arrears
If your account is insufficient to pay your amount due, your account goes into arrears, and the pay-per-use service mesh enters a grace period. After you top up your account, Huawei Cloud will bill you for expenditures generated by the service mesh during the grace period. You can view the expenditures on the Overview page of Billing Center.
If your account is still in arrears after the grace period ends, the service mesh enters a retention period and turns to Frozen. You cannot perform any operations on the service mesh.
If you do not bring your account balance current before the retention period ends, the service mesh resources will be released and the data cannot be restored.
- If the outstanding amount for pay-per-use resources is still not paid off, 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.
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