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

Supported CVM Models for General Nodes

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-12-10 11:03:32

Background

To enhance the provision of container services, TKE conducts availability tests for container environments on the device models supported by general nodes. These tests primarily cover multiple application modules such as container network modes, storage, public images, node initialization, and GPU drivers. The following table lists the general node device models that can be created on the TKE console.
Note:
The range of device models supported by the TKE console for creating general nodes does not correspond directly with those of the CVM console. If your business requires adaptation to new device models, you may submit a service ticket.

Supported Device Models for General Nodes

Instance Type
Device Model
Standard type
S1、S2、S2ne、S3、S3ne、S4、S4m、S5、S5se、S5t、S6、S6t、SA1、SA2、SA2a、SA3、SK1、SN3ne、SR1、SW3a、SW3b、SW3ne、SA4、SA5、S8
Premium type
RS2t、RS3t、RS4t、RS5t
Computational type
C2、C3、C4、C5、C6、TC3、CN3
High-I/O type
I1、I2、I3、I6t、IT2、IT3、IT3a、IT3b、IT3c、IT5、ITA5
Memory type
M1、M2、M3、M4、M5、M6、M8、M6ce、M6mp、M6p、MA2、MA3、MA4、MA5、MA9、MA9e
High-performance type
HCCG5v、HCCIC5、HCCPNV4h、HCCTG5v、HCCPNV4sne(HCCPNV4sn)、HCCPNV5v、HCCPNV5vp、HCCPNV5、HCCPNV5x
GPU model
GI1、GI3X、GN10S、GN10X、GN10Xp、GN6、GN6S、GN7、GN8、GNV4、GT4、PNV4、PNV4ne、PNV5、GC49、PNV5b、PNV5i
Big data type
D1、D2、D3
Bare metal
BMD2、BMD3、BMD3c、BMD3s、BMDA2、BMI5、BMIA2、BMIA2m、BMM5r、BMS4、BMSA2、BMSC4、BMM6i、BMTGC39me(BMGC39me)、BMG5e、BMG5n、BMG5i、BMG5t、BMGY5、BMGNV4、BMSA3、BMIA3、BMS5
Others
CHC、CN10X、BC1
Note:
1. Before using Cloud Bare Metal (CBM), navigate to Instance Specification to confirm the device model configurations, such as whether the mounting of elastic NICs is supported and whether the mounting of cloud disks is supported.
1.1 For device models that do not support the mounting of elastic NICs, general nodes cannot be added to clusters in VPC-CNI network mode. In this case, you can use the GR mode.
1.2 For device models that do not support the mounting of cloud disks, PVCs cannot be bound to pods.
2. Regarding high-performance HCC models:
2.1 HCCG5v, HCCIC5, HCCPNV4h, and HCCTG5v only support public images of CentOS 7.6, Ubuntu 18.04.1, and TencentOS Server 2.4 (TK4).
2.2 HCCPNV5vp only supports custom images. Please submit a ticket and contact CVM after-sales support to provide them.
2.3 HCCPNV5 and HCCPNV5x only support public images of TencentOS Server 3.1 (TK4) UEFI. Please submit a ticket and contact CVM after-sales support to enable an allowlist.
3. ARM device models SR1 and SK1 only support images of TencentOS Server 2.4 for ARM 64 (TK4) and CentOS 8.2 (ARM).
4. Consumer-grade card models (such as GC49) require manual driver installation. You can specify the driver installation script when creating a node or use a pre-installed driver custom image; otherwise, the node initialization might fail due to undetected drivers.
5. Only the SA2, S5, C3, and C4 device models support Red Hat images.
6. The qGPU feature is only available for native nodes, currently supporting T4 and V100 card models. For details, see Using qGPU.


Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan