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

Native Node Pricing

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2025-12-22 18:10:41

Pricing

Note:
Native node is a TKE cloud product billed separately. Its pricing is different from that of that of the Cloud Virtual Machine (CVM) service. The billing information of different specifications of native nodes is subject to that displayed on the console.
TKE native nodes support multiple types of CVM instances. You can select appropriate instances to deploy based on your application scale and business characteristics. TKE charges resources (including CPU, memory, GPU, and system disk resources) consumed by native node instances according to the instance type and resource specifications.
Billing formula: Fees = Unit price of the native node instance resource configuration * Running time
Billing Item
Description
Instance type
Instance types supported by the current native node are as follows: (For more information, see CVM instances)
Standard: S2, S4, S5, SA2, SA3, S6, SA5, SA4, S7, S8, SA9
Computing: C3, C4, C5, C6
Memory optimized: M3, MA3, MA4, M5, M6, M8
GPU: GN7, GNV4, PNV4, GN10X, GN10Xp, GT4
High I/O: IT5, ITA5
Resource specifications
Resource specifications supported by the current native node are as follows: (Subject to those displayed on the console)
CPU: Two cores or more
Memory: 2 GB or more
System disk: Premium Cloud Storage or SSD, 50-1024 GB
GPU: Only GPU native node instances contain GPU resources and support only entire GPUs.

Billing Mode

Tencent Kubernetes Engine (TKE) provides two billing modes for the native node instance: yearly/monthly subscription and pay-as-you-go, which are suitable for user demands in different scenarios. The details are as follows:
Billing Mode
Yearly/Monthly Subscription
Pay-as-you-go
Payment method
Prepaid.
Postpaid (Fees are frozen upon purchase and settled hourly)
Billing unit
USD/month.
USD/second
Unit price
Lower.
Higher.
Minimum usage duration
At least one month.
Billed by second and settled by hour. You can purchase or release resources at any time.
Use cases
Suitable for mature businesses with long-term and stable node resource demands.
Suitable for periodic computing scenarios such as transcoding, big data, and e-commerce flash sale campaigns, or tidal online service scenarios where Horizontal Pod Autoscaler (HPA) is enabled.

Yearly/Monthly Subscription

Billing formula: Payment amount = Number of applied native node instances x Unit price of the native node instance resource configuration (monthly subscription) x Monthly subscription duration
Yearly/Monthly subscription is a prepaid billing mode for TKE native node instances. It requires paying fees for one or more months, even years in advance. It is generally more cost-effective compared to the pay-as-you-go billing mode. Before the purchase of monthly subscription native node instances, check the available balance in your cloud account. If the balance is insufficient to cover the amount deducted by the system, top up before the purchase.

Pay-as-you-go

Billing formula: Fees = Number of requested native node instances × Unit price of the native node instance resource configuration (by usage) × Usage duration When you activate a pay-as-you-go native node instance, the fees (including CPU, memory, GPU, and system disk fees) for 1-hour usage based on the resource configuration unit price will be frozen in your account balance as a deposit. You will then be billed by the hour (Beijing time) for your usage over the past hour. When you purchase a native node instance, the unit price will be listed as an hourly fee. However, you will actually be billed by the second and the fees will be rounded to the nearest two decimal places. Billing starts from the second the native node instance is purchased and stops the second the instance is terminated. When the instance is terminated, the frozen amount will be unfrozen.

References

Ajuda e Suporte

Esta página foi útil?

comentários