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 EnginePurchase GuidePurchasing a Super NodeResource Specifications

Resource Specifications

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2023-05-06 17:36:46

Overview

TKE serverless clusters free you from managing cluster nodes. However, to properly allocate resources and accurately calculate fees, you need to specify resource specifications for Pods when deploying a workload. Tencent Cloud allocates computing resources to the workload and calculates the corresponding fees based on the specified specifications.
When you use the Kubernetes API or kubectl to create a workload for a TKE serverless cluster, you can use annotations to specify resource specifications. If annotations are not used, the TKE serverless cluster will calculate the specifications based on the container parameters set for the workload, such as Request and Limit. For more information, see Specifying Resource Specifications.
Note
The resource specifications indicate the maximum amount of resources available for containers in a Pod.
The following tables list the supported CPU and GPU specifications. Ensure that allocated resources do not exceed the supported specifications.
The total amount of resources specified by Request for all the containers in a Pod cannot exceed the highest Pod specification.
The amount of resources specified by Limit for any container in a Pod cannot exceed the highest Pod specification.

CPU Specifications

The following table lists CPU specifications that TKE serverless clusters provide for Pods in all regions where CPU resources are supported. TKE serverless clusters also provide a set of CPU options. Different CPU sizes correspond to different memory ranges. Select the CPU specification as needed when creating a workload.

Intel

CPU (Cores)
Memory Range (GiB)
Memory Range Granularity (GiB)
0.25
0.5, 1, 2
-
0.5
1, 2, 3, 4
-
1
1–8
1
2
2, 4–16
1
4
8–32
1
8
16–32
1
12
24–48
1
16
32–64
1

Star Lake AMD

Based on Tencent Cloud’s self-developed Star Lake servers, EKS provides reliable, secure, and stable high performance. For more information, see Standard SA2.
CPU (Cores)
Memory Range (GiB)
Memory Range Granularity (GiB)
1
1–4
1
2
2–8
1
4
4–16
1
8
8–32
1
16
32–64
1

GPU Specifications

The following table lists the GPU specifications that TKE serverless clusters provide for Pods. Different GPU card models and sizes map to different CPU and memory options. Select the GPU specification as needed when creating a workload.
Note
If you want to create, manage, and use GPU workloads using a YAML file, see Annotation Description for reference.
GPU Model
GPU
CPU (Cores)
Memory (GiB)
NVIDIA Tesla V100 - 1
1
8
40
NVIDIA Tesla V100 - 2
2
18
80
NVIDIA Tesla V100 - 4
4
36
160
NVIDIA Tesla V100 - 8
8
72
320
1/4 NVIDIA T4 - 1/4
1
4
20
1/2 NVIDIA T4 - 1/2
1
10
40
NVIDIA T4 - 1
1
8
32
NVIDIA T4 - 1
1
20
80
NVIDIA T4 - 1
1
32
128
NVIDIA T4 - 2
2
40
160
NVIDIA T4 - 4
4
80
320
NVIDIA A10 - PNV4 - 1
1
28
116
NVIDIA A10 - PNV4 - 2
2
56
232
NVIDIA A10 - PNV4 - 4
4
112
466
NVIDIA A10 - PNV4 - 8
8
224
932
NVIDIA A10 - GNV4 - 1
1
12
44
NVIDIA A10 - GNV4v - 1/4
1
6
24
NVIDIA A10 - GNV4v - 1/2
1
14
58
NVIDIA A10 - GNV4v - 1
1
28
116
Topik sebelumnya: Refund Instructions for Yearly/Monthly Subscription InstancesTopik selanjutnya: Super Node Pricing

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan