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 Parameters

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-12-10 11:03:32
Parameter
Support Details
Description
Model
Standard: S2, S4, S5, SA2, SA3, S6, SA5, SA4, S7, S8, SA9, S9, S9e, and SA9e
Compute optimized: C3, C4, C5, and C6
Memory Optimized: MA2, M3, MA3, M5, M6, M8, and MA4
GPU Optimized: GN7, GNV4, PNV4, GN10X, GN10Xp, GT4, Pnv5i, Pnv5b, Pnv5, Pnv6, GC49d, and GC49
High-IO Type: IT5 and ITA5
BeFast:BF1
The display of console models is related to the remaining resources of the selected availability zone. For more model requirements, you can seek help by Submit a ticket. Moreover, native node pools support several alternative machine types with the same configuration specifications. You can go to the Node Pool Detail Page to set up.
System disk
High-performance Cloud Disk, SSD Cloud Disk
It is recommended that the system disk be at least 100GB.
Data disk
High-performance Cloud Disk, SSD Cloud Disk, General Purpose SSD, Enhanced SSD
It is recommended that the data disk be at least 50GB; by default, a data disk is not bound.
Public network bandwidth
Supports binding an EIP
By default, the node's public network bandwidth is not enabled. For details, please see Enabling the public network access.
Operating system
TencentOS Server
Relying on the Tencent Cloud Virtualization Platform and through kernel optimizations, it provides support for Cloud Native Resource Isolation Technology, and fully tunes parameters for container application scenarios.
Node login
SSH login
Default node login is enabled. You can enable and distribute SSH Key for nodes to be logged in to via the console. For details, see Enable SSH Key Login.
GPU driver
Drivers 450/470/515/525
When creating a node pool, you can select the target driver below the model selection.
Runtime
Supports Containerd only
For clusters with Kubernetes version 1.16 and above, the supported Containerd version is 1.6.9.
Kubernetes
K8s major version ≥ 1.16
Some K8s versions have specific minor version requirements, as follows: v1.16.3-tke.28 and above; v1.18.4-tke.26 and above; v1.20.6-tke.21 and above.
Operation and Maintenance Parameters
Supports setting parameters for Kubelet, Kernel, Hosts, Nameservers
For more information, see Management Parameters.
Initialization Script
Supports two phases: before and after node initialization
You can provide an initialization script when creating a node pool.
Node Auto Scaling
Supported
For details, please see Native Node Scaling.
Node Specification Enlargement
Supported, provides a scalable dedicated scheduler for native nodes
qGPU
Supported
For details, please see qGPU Overview.
Memory Compression
Supported
For more details, see the Memory Compression User Guide.
Preemptible Jobs
Supported
For more details, see the Preemptible Job feature description.
QoSAgent
Supported
Provides multi-dimensional fine scheduling capabilities such as CPU Priority, CPU Burst, Memory/Network/Disk IO QoS enhancements, improving cluster resource utilization while ensuring quality stability. For more details, see Fine Scheduling.
Fault Self-Healing
Supported
Based on TKE's self-developed intelligent operations product Cloud Explorer, it provides multi-dimensional fault self-healing capabilities, comprehensively enhancing node stability and operational efficiency. For more details, see Fault Self-Healing Rules.
In-Place Scaling
Supported
For more details, see Enable Pod In-Place Scaling.



Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan