tencent cloud

While using TKE services, you need to consider the service quota applied to TKE, CVM, and managed clusters.

TKE Quota Limit

The default TKE quota for each user is as follows. If you want to increase the quota, submit a ticket for application.

Note：

From October 21, 2019, the maximum node quota for a cluster has been adjusted to at least 5,000.

Item	Default Value	Where to Check	Quota Increase Allowed or Not
Clusters in a region	20	Bottom-right section of the TKE overview page	Yes
Nodes in a cluster	5,000
Image namespaces in a region	10
Image repositories in a region	500
Tags of an image	100

CVM Quota Limit

CVM instances generated by TKE are subject to purchase limits. For more information, see Purchase Limits. If you need more quotas than the default, submit a ticket for application.

Item	Default Value	Where to Check	Quota Increase Allowed or Not
Pay-as-you-go CVM instances in an AZ	30 or 60	CVM Instances page - Resources in each region	Yes

Cluster Configuration Limit

Note：

Cluster configuration limits the cluster size and cannot be modified currently.

Item	IP Address Range	Affected Scope	Where to Check	Modification Allowed or Not
VPC network - Subnet	Custom	Number of nodes that can be added to the subnet	VPC subnet list page for the cluster - Number of available IP addresses	No You can use a new subnet
Container CIDR block	Custom	Maximum number of nodes per cluster Maximum number of services per cluster Maximum number of Pods per node	Basic information page for the cluster - Container CIDR block	No

K8s Resource Quota Description

Note：

The following quotas are automatically applied from April 30, 2022 (UTC +8) and cannot be adjusted. You can increase the resource quota by upgrading the cluster model.
To adjust your quota, submit a ticket for application.

Run the following command to check the quota:

kubectl get resourcequota tke-default-quota -o yaml

To check the tke-default-quota object of a specified namespace, add --namespace to specify the namespace.

Note：

• Other K8s resource limit means that the number of all K8s resources in the cluster except Pod, Node, and ConfigMap cannot exceed this value. For example, for an L100 cluster, the number of ClusterRole, Service, Endpoint, and other K8s resources cannot exceed 10,000.

• CRD refers to the sum of all CRDs in the cluster. If the number of some CRDs increases, the number of other CRDs will decrease.

Cluster Model	Pods	ConfigMap	CRDs/Other K8s Resources
L5	600	256	1,250
L20	1,500	512	2,500
L50	3,000	1,024	5,000
L100	6,000	2,048	10,000
L200	15,000	4,096	20,000
L500	30,000	6,144	50,000
L1000	90,000	8,192	100,000
L3000	150,000	10,240	150,000
L5000	200,000	20,480	200,000

Namespace quota

By default, each namespace has the same margin (margin = quota for the current cluster level - amount already used by the entire cluster). If you create resources in a namespace, the margin will decrease, and the amount available in other namespaces will decrease accordingly after a certain period of time.

If you want to customize the allocation ratio, you can create a tke-quota-config ConfigMap under kube-system to specify the margin allocation ratio for each namespace.

The following example sets the margin allocation ratio to 50% for the default namespace, 40% for the kube-system namespace, and 10% for the rest of the namespaces. If the sum of the set percentages exceeds 100%, TKE considers the ratio invalid and will use the default allocation policy.

apiVersion: v1
data:
  default: "50"
  kube-system: "40"
kind: ConfigMap
metadata:
  name: tke-quota-config
  namespace: kube-system