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 EngineCloud Native Service Guide TKE Serverless Cluster Guide Purchasing a TKE Serverless ClusterPurchase Limits

Purchase Limits

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2024-12-19 22:29:21

Use Restrictions

Before using a TKE serverless cluster, you need to sign up for a Tencent Cloud account and complete identity verification.

Supported Regions

For more information on regions where TKE serverless clusters are supported, see Regions and Availability Zones. For more information on resource specifications, see Resource Specifications.

Resource Quotas

Cluster and Pod limits

Resource
Limit
Description
Clusters in one region
5
Includes clusters that are being created and running.
Pods in one cluster
100
Includes all namespaces, workloads, and stateless and stateful pods.
Pod replicas for one workload
100
Includes all stateless and stateful pods in the workload.
The largest container instance size for the same region
500
Includes all stateless and stateful container instances.

Other limits

All Pods in a TKE serverless cluster are independent computing and network instances in the cloud, which can be regarded as CVM instances and are therefore subject to the following limits:
1. When a workload is created, each Pod will be associated with a security group by default, and all Pod replicas in the same workload will be associated with the same security group. Each Pod is a CVM instance for the security group and is subject to the quota on the number of CVM instances that can be associated with a security group.
2. When CLB Services are used, each Pod bound to the CLB instance is a CVM instance for the CLB instance and is subject to the quota on the number of servers that can be bound to a forwarding rule in a CLB instance.

Applying for a higher quota

If the number of required resources exceeds the quota limit shown in the preceding table, you can submit a ticket to apply for a higher quota. Tencent Cloud will assess your actual needs and increase your quota as appropriate.
1. Submit a ticket. Select Others > Create Now to enter the ticket creation page.
2. In the Problem description field, enter a description such as "I want to apply for a higher quota for the TKE serverless cluster." Specify the target region, object, and quota. Enter your mobile number and other information as instructed.
3. Click Submit Ticket.
Topik sebelumnya: Billing OverviewTopik selanjutnya: Creating a Cluster

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan