Detailed information on all quotas and service limits - Container Service for Kubernetes

This topic describes the quotas and limits that apply when you use Alibaba Cloud Container Service for Kubernetes, including product and cluster configuration limits, single-cluster capacity limits, cluster quotas, and quotas for underlying cloud services.

Limits

Product and Cluster Configuration Limits

Before enabling Container Service for Kubernetes and while using ACK clusters, the following usage limits apply.

Limit Item	Description
Account verification	Before creating an ACK cluster, complete identity verification and activate Container Service for Kubernetes. For more information, see Activate Container Service for Kubernetes.
Cluster configuration	After creating an ACK cluster, you cannot change the following configurations. You cannot change the cluster VPC. You cannot directly change the cluster type. For example, an ACK dedicated cluster cannot be directly changed to an ACK managed cluster. Currently, hot migration from ACK dedicated clusters to ACK managed clusters Pro Edition is supported. For more information, see Hot Migrate an ACK Dedicated Cluster to an ACK Managed Cluster Pro Edition. Cluster specifications cannot be directly changed, such as changing an ACK managed cluster Pro Edition to an ACK managed cluster Basic Edition. Currently, hot migration from ACK managed clusters Basic Edition to ACK managed clusters Pro Edition is supported. For more information, see Hot Migrate an ACK Managed Cluster Basic Edition to an ACK Managed Cluster Pro Edition. Network plugins (Terway, Flannel) do not support mutual conversion.
ECS instance (node instance) configuration	Pay-as-you-go, subscription, and spot instance billing methods are supported. In the ECS console, convert pay-as-you-go instances to subscription instances. Because underlying dependent products such as ECS have quota and inventory limits, only some nodes may be created successfully when you create, scale out, or auto-scale clusters. Node specifications must be 4 CPU cores and 8 GB memory or higher. For more information, see ECS Instance Type Configuration Recommendations.
Cluster control plane component access traffic	When accessing cluster control plane components (API Server, etcd) via API or command line, bandwidth limits may trigger rate limiting and cause read failures when reading many cluster events at once. Use the events tab to query cluster events, or add pagination parameters to API or command line requests to reduce the single request volume (for example: `--chunk-size=500`). For more information, see Scenario 1: Monitor Cluster Events Using NPD and SLS Kubernetes Event Center. In addition, if you frequently encounter rate limiting issues in an ACK Basic cluster, migrate to an ACK Pro cluster. For more information, see Hot migrate an ACK Basic cluster to an ACK Pro cluster.

Single Cluster Capacity Limits

ACK managed cluster Pro Edition and ACK managed cluster Basic Edition differ in scenarios and supported capacity.

ACK managed cluster Pro Edition: Recommended for enterprise production environments.
In the ACK managed cluster Pro Edition, when the Terway network plug-in is configured and IPvlan is enabled, the maximum number of pods is 50,000, and the total number of mappings between Services and pods is limited to 64,000 for a cluster with 5,000 nodes.
ACK managed cluster Basic Edition: For personal testing or learning only.

The following table describes the maximum capacity for different resource types within a single cluster.

Type	ACK managed cluster Pro Edition	ACK managed cluster Basic Edition
etcd storage capacity	8 GB	2 GB
Total size of etcd objects for each resource type	800 MB	200 MB
Node	Flannel: 200 by default, 1,000 maximum Terway: 5,000 by default, 15,000 maximum	10
Pod	150,000 Depends on the network plugin and available Pod CIDR block configuration	300
Namespace	10,000	100
ConfigMap	30,000	300
Secret	100,000	1,000
PVC	100,000	1,000
PV	100,000	1,000
Service	10,000	100
Role	50,000	500
RoleBinding	50,000	500
CRD	100,000	1,000
Number of CR resources per CRD type	100,000	1,000

Quotas

Cluster Quotas

The following table lists only the default quotas for each item. To view the adjustable quotas for this product and their upper limits and to request an increase, go to Quota Center.
To make the requested increase in the maximum number of node pools per cluster quota take effect, you must also request an increase in the total number of scaling groups quota for Auto Scaling (ESS). Log on to the Quota Platform to submit a request.
②: The maximum number of pods per node is affected by the cluster network plug-in.
- Flannel: Affected by the CIDR block planning during cluster creation. Refer to the following table. You cannot request an increase for this quota.
- Terway: Depends on the number of elastic network interfaces (ENIs) provided by the ECS instance type. Select ECS instance types with higher specifications and newer models.

ACK managed cluster

Dimension	Basic Edition	Pro Edition
Maximum number of clusters per Alibaba Cloud account	2	100
Maximum number of node pools per cluster^①	10	100
Maximum number of nodes per cluster	10	Using Flannel container network plugin: 200 by default, 1,000 maximum Using Terway container network plugin: 5,000 by default, 15,000 maximum
Maximum number of serverless pods per cluster	1,000	50,000 Important If many pods are associated with services, keep the number below 20,000.
Maximum Pods per single node^②	Using Flannel container network plugin: 256 Using Terway container network plugin: The pod limit per node is determined by the node specifications. For more information, see Calculate Pod Limit per Node
Quota increase method	Cannot be requested	log on to the Quota Center console and submit an application

ACK dedicated cluster

Maximum number of clusters per Alibaba Cloud account: 0 (Creation stopped)
Maximum node pools per cluster^①: 100
Maximum number of nodes per cluster:
- Using Flannel container network plugin: 200 by default, 1,000 maximum
- Using Terway container network plugin: 5,000 by default, 15,000 maximum
Maximum number of Pods per node^②:
- Using Flannel container network plugin: 256
- Using Terway container network plugin: The pod limit per node is determined by the node specifications. For more information, see Calculate Pod Limit per Node
Quota increase method:
log on to the Quota Center console and submit an application

ACK serverless cluster

Dimension	Basic Edition	Pro Edition
Maximum number of clusters per Alibaba Cloud account	2	100
Maximum number of pods per cluster	1,000	50,000 Important If many pods are associated with services, keep the number below 20,000.
Quota increase method	log on to the Quota Center console and submit an application

ACK Edge Cluster

Dimension	Basic Edition	Pro Edition
Maximum number of clusters per Alibaba Cloud account	2	100
Maximum number of node pools per cluster^①	10	100
Maximum number of nodes per cluster	10	1,000
Maximum Pods per node^②	256	256
Quota increase method	Cannot be requested	log on to the Quota Center console and submit an application

Registered Clusters

Maximum number of clusters per Alibaba Cloud account: 5
Maximum node pools per cluster^①: 100
Maximum Pods per node^②: 256
Quota increase method:
log on to the Quota Center console and submit an application

Underlying Cloud Product Quotas

Product Type	Limit Item	Default Limit	Quota Increase Method
Elastic Compute Service	Alibaba Cloud Resource Orchestration Service (ROS) quota	100	submit a ticket
	On-demand instance vCPU limit	500 cores	submit a ticket
	Purchase high-specification on-demand instances (instances with more than 16 cores)	Instance types with fewer than 16 vCPU cores (excluding 16)	submit a ticket
	Preemptible instance vCPU limit	800 cores	submit a ticket
	Convert pay-as-you-go to subscription	Unsupported instance types (families): t1, s1, s2, s3, c1, c2, m1, m2, n1, n2, e3	submit a ticket
	Maximum number of ECS instances in a single scaling group for ESS	2,000	log on to the Quota Center console and submit an application
	Operating system	Nodes that run the following operating systems can be added to an ACK cluster: Alibaba Cloud Linux CentOS 7.x Note CentOS 8.x and later are not supported. Windows Server 2019 and Windows Server version 1809 and later.	None
Network	Applies only to clusters with the Flannel network plug-in Custom route entries per route table (excluding dynamically propagated route entries).	200	See General Quotas.
	vSwitches per VPC.	150
	VPCs in a single region.	10
	Maximum number of private IP addresses that a security group in a VPC can contain per Alibaba Cloud account in a region	Basic security group: 6,000 Enterprise security group: 65,535	For basic security groups, apply on the Quota Center.
	Maximum number of security groups for a single Alibaba Cloud account in a specific region	To view or increase the quota, use the quota ID `q_security-groups`. For more information, see View or increase ECS quotas.
	Maximum number of ENIs (secondary ENIs) that a single Alibaba Cloud account can create in a specific region	To view the quota, use the quota ID `q_elastic-network-interfaces`. For more information, see View or increase ECS quotas.	View or increase ECS quotas
	Pay-as-you-go EIPs per account (excludes subscription EIPs)	20	Increase the quota on the Quota Management page or Quota Center.
Server Load Balancer	Number of CLB instances that can be created per Alibaba Cloud account	30	Choose one of the following methods as needed: Go to the Server Load Balancer Quota Management page to increase the slb_quota_instances_num quota. For more information, see Quota management. Go to Quota Center to increase the quota. For more information, see Manage CLB quotas.
	Number of backend servers that can be added to a CLB instance	200	Choose one of the following methods as needed: Go to the Server Load Balancer Quota Management page to increase the slb_quota_backendservers_num quota. For more information, see Quota management. Go to Quota Center to increase the quota. For more information, see Manage CLB quotas.
	Number of listeners that can be added to a CLB instance	50	Choose one of the following methods as needed: Go to the Server Load Balancer Quota Management page to increase the slb_quota_listeners_num quota. For more information, see Quota management. Go to Quota Center to increase the quota. For more information, see Manage CLB quotas.
	Maximum number of times the same server can be added as a CLB backend server	50 times	None
Elastic Block Storage	Quota for pay-as-you-go cloud disks for an account across all regions	Number of instances across all regions under the account × 5. Each account can create a minimum of 10 pay-as-you-go cloud disks.	submit a ticket
Elastic Block Storage	Quota for pay-as-you-go cloud disk capacity used as data disks for an account	This depends on ECS usage, region, and cloud disk type. View it on the privilege quota page. For more information, see Elastic Block Storage.	submit a ticket

References

Different cluster types have precautions and important risky operations for different features. Please read them carefully. For more information, see Usage notes and important risky operations.
To ensure that your cluster applications are stable and reliable, see Recommended Workload Configurations to properly configure your cluster, workloads, and components.
You can increase the number of supported Pods by adding more nodes. However, an excessively large cluster may affect its availability and performance. Therefore, you should design and use your cluster with a reasonable scale. For more information, see Recommendations for large-scale clusters.