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
DokumentasiTencent Kubernetes EngineCloud Native Service GuideCloud Service for etcdPurchase Guide

Purchase Guide

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-03-19 18:30:11

Billing Mode

Cloud Service for etcd supports the following 2 billing modes:
Billing Mode
Payment Method
Billing Cycle
Applicable Scenario
Monthly subscription
Prepayment. Fees are paid when an instance is created.
Month
Apply to the businesses of stable scale with long-term resource requirements. The fees are lower than that of the pay-as-you-go mode. The longer the purchase duration, the higher the discount.
Pay-as-you-go
Postpayied. Resources are applied on-demand and are charged based on the actual usage upon settlement.
Hour
Apply to short-term businesses with on-demand usage needs. Instances can be released immediately after use to save costs.

Instance Specifications

Specifications of Cloud Service for etcd instances are defined in dimensions of CPU, memory, and number of replicas.

Pay-as-You-Go

If the usage duration is less than 1 hour, fees of 1 hour are charged.
Node Specifications
Number of Nodes
USD/Hour
1C2G
3
0.33 USD
5
0.41 USD
2C4G
3
0.49 USD
5
0.65 USD
4C8G
3
0.73 USD
5
1.05 USD
8C16G
3
1.21 USD
5
1.85 USD
8C32G
3
1.65 USD
5
2.58 USD
16C64G
3
3.04 USD
5
4.91 USD
32C128G
3
5.84 USD
5
9.56 USD

Monthly Subscription

Node Specifications
Number of Nodes
USD/Month
1C2G
3
217.06 USD
5
269.38 USD
2C4G
3
321.7 USD
5
426.34 USD
4C8G
3
478.66 USD
5
687.94 USD
8C16G
3
792.57 USD
5
1,211.13 USD
8C32G
3
1,078.68 USD
5
1,687.97 USD
16C64G
3
1,992.61 USD
5
3,211.19 USD
32C128G
3
3,820.48 USD
5
6,257.65 USD

Payment Overdue

Notifications of Payment Overdue and Resource Expiration

The platform will send notifications via SMS messages, emails, and Message Center before instance resources expire or overdue payment occurs.

Recycling Mechanism

If pay-as-you-go is adopted, instances can still be used within 24 hours after overdue payment occurs. After 24 hours, instances will be isolated, and billing will stop. Isolated instance cannot be accessed. Users can top up to recover instances within 7 days after the isolation. If instances are not recovered 7 days later, they will be released, and resources will be recycled, which cannot be restored.
If monthly subscription is adopted, instances can still be used within 3 days after overdue payment occurs. After 3 days, instances will be isolated, and billing will stop. Isolated instance cannot be accessed. Users can top up to recover instances within 7 days after the isolation. If instances are not recovered 7 days later, they will be released, and resources will be recycled, which cannot be restored.

Topik sebelumnya: OverviewTopik selanjutnya: Refund Instructions for Monthly Subscription Instances

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan