tencent cloud

Tencent Kubernetes Engine

Release Notes and Announcements
Release Notes
Announcements
Release Notes
Product Introduction
Overview
Strengths
Architecture
Scenarios
Features
Concepts
Native Kubernetes Terms
Common High-Risk Operations
Regions and Availability Zones
Service Regions and Service Providers
Open Source Components
Purchase Guide
Purchase Instructions
Purchase a TKE General Cluster
Purchasing Native Nodes
Purchasing a Super Node
Getting Started
Beginner’s Guide
Quickly Creating a Standard Cluster
Examples
Container Application Deployment Check List
Cluster Configuration
General Cluster Overview
Cluster Management
Network Management
Storage Management
Node Management
GPU Resource Management
Remote Terminals
Application Configuration
Workload Management
Service and Configuration Management
Component and Application Management
Auto Scaling
Container Login Methods
Observability Configuration
Ops Observability
Cost Insights and Optimization
Scheduler Configuration
Scheduling Component Overview
Resource Utilization Optimization Scheduling
Business Priority Assurance Scheduling
QoS Awareness Scheduling
Security and Stability
TKE Security Group Settings
Identity Authentication and Authorization
Application Security
Multi-cluster Management
Planned Upgrade
Backup Center
Cloud Native Service Guide
Cloud Service for etcd
TMP
TKE Serverless Cluster Guide
TKE Registered Cluster Guide
Use Cases
Cluster
Serverless Cluster
Scheduling
Security
Service Deployment
Network
Release
Logs
Monitoring
OPS
Terraform
DevOps
Auto Scaling
Containerization
Microservice
Cost Management
Hybrid Cloud
AI
Troubleshooting
Disk Full
High Workload
Memory Fragmentation
Cluster DNS Troubleshooting
Cluster kube-proxy Troubleshooting
Cluster API Server Inaccessibility Troubleshooting
Service and Ingress Inaccessibility Troubleshooting
Common Service & Ingress Errors and Solutions
Engel Ingres appears in Connechtin Reverside
CLB Ingress Creation Error
Troubleshooting for Pod Network Inaccessibility
Pod Status Exception and Handling
Authorizing Tencent Cloud OPS Team for Troubleshooting
CLB Loopback
API Documentation
History
Introduction
API Category
Making API Requests
Elastic Cluster APIs
Resource Reserved Coupon APIs
Cluster APIs
Third-party Node APIs
Relevant APIs for Addon
Network APIs
Node APIs
Node Pool APIs
TKE Edge Cluster APIs
Cloud Native Monitoring APIs
Scaling group APIs
Super Node APIs
Other APIs
Data Types
Error Codes
TKE API 2022-05-01
FAQs
TKE General Cluster
TKE Serverless Cluster
About OPS
Hidden Danger Handling
About Services
Image Repositories
About Remote Terminals
Event FAQs
Resource Management
Service Agreement
TKE Service Level Agreement
TKE Serverless Service Level Agreement
Contact Us
Glossary

Payment Overdue

PDF
Focus Mode
Font Size
Last updated: 2024-12-23 15:39:02
If your account has overdue payment, a notification will be sent to you. Once receiving it, please go to the Billing Center in the console and pay the past due charges in time to prevent your business from being affected. This document will provide detailed information on overdue payment of native nodes.

Alerting

Reminder Type
Description
Expiration
Seven days before cluster resource expiration, the system will send an expiration alert to your Tencent Cloud account creator, global resource collaborators, and financial collaborators by email and SMS.
Overdue payment
On the day of and after cluster resource expiration, the system will send an overdue payment alert to your Tencent Cloud account creator and all collaborators by email and SMS.

Repossession

Note:
Suspension: When the resource of a user is suspended, the user cannot use the resource any more. However, data of the resource is not deleted, and the user can resume the resource.
Release: Data of a resource is deleted, and the resource cannot be resumed.

Pay-as-you-go instance repossession mechanism

Starting from the point when your account balance becomes negative, the native node instances are still available for the next two hours, and the billing continues. Two hours later, if your account is still not topped up to a balance greater than zero, the native node instances will be suspended and released (the node resources will be terminated, and data cannot be restored).
If your account is topped up to a balance greater than zero two hours after your account has overdue payments, the fees of the native node instances will be calculated and deducted according to the pay-as-you-go billing rules.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback