tencent cloud

Tencent Kubernetes Engine

소식 및 공지 사항
릴리스 노트
제품 릴리스 기록
제품 소개
제품 장점
제품 아키텍처
시나리오
제품 기능
리전 및 가용존
빠른 시작
신규 사용자 가이드
표준 클러스터를 빠르게 생성
Demo
클라우드에서 컨테이너화된 애플리케이션 배포 Check List
TKE 표준 클러스터 가이드
Tencent Kubernetes Engine(TKE)
클러스터 관리
네트워크 관리
스토리지 관리
Worker 노드 소개
Kubernetes Object Management
워크로드
클라우드 네이티브 서비스 가이드
Tencent Managed Service for Prometheus
TKE Serverless 클러스터 가이드
TKE 클러스터 등록 가이드
실습 튜토리얼
Serverless 클러스터
네트워크
로그
모니터링
유지보수
DevOps
탄력적 스케일링
자주 묻는 질문
클러스터
TKE Serverless 클러스터
유지보수
서비스
이미지 레지스트리
원격 터미널
문서Tencent Kubernetes Engine

Native Node Pricing

포커스 모드
폰트 크기
마지막 업데이트 시간: 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

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백