This topic describes the limits that apply when you use Container Service for Kubernetes (ACK) clusters.
Before you get started with ACK, take note of the following limits:
- Before you purchase ACK instances, you must complete real-name verification.
- After an ACK cluster is created, you are not allowed to perform the following operations:
- You cannot change the virtual private cloud (VPC) of the cluster.
- You cannot change the type of the cluster. For example, you cannot change a dedicated Kubernetes cluster to a managed Kubernetes cluster.
- You cannot change the network plug-in.
- You cannot change the volume plug-in.
- You cannot migrate applications across namespaces.
- The following limits are imposed on Elastic Compute Service (ECS) instances that run
in ACK clusters:
- ECS instances support the pay-as-you-go and subscription billing methods. Other resources, such as Server Load Balancer (SLB) instances, support only the pay-as-you-go billing method. You can change the billing method from pay-as-you-go to subscription in the ECS console.
- When you create clusters, expand clusters, or perform auto scaling, you may fail to create nodes due to insufficient resource quota or inventory.
- If you want to create subscription ECS instances when you create a cluster, you may
fail to create the ECS instances due to resource quota limits or inventory availability.
After a subscription ECS instance is created, you cannot release the ECS instance
before the subscription expires.
Note To avoid these issues, we recommend that you create pay-as-you-go ECS instances when you create a cluster. You can change the billing method from pay-as-you-go to subscription in the ECS console based on your requirements.
- Requirements for ECS specifications: You must select ECS instances with 2 or more vCPU cores and memory sizes must be greater than 4 GiB.
Limits on the quota of ACK clusters
|Cluster type||Maximum number of clusters within an Alibaba Cloud account||Maximum number of nodes in a cluster||Maximum number of pods on a node||Adjustable|
|Professional managed Kubernetes cluster||100||1000||256|
|Standard managed Kubernetes cluster||20||40||256||N/A|
|Dedicated Kubernetes cluster||20||40||256||N/A|
|Serverless Kubernetes (ASK) cluster||5||N/A||N/A|
|Edge Kubernetes cluster||20||100||256|
|Registered external Kubernetes cluster||5||N/A||N/A|
Quotas of underlying cloud resources
|Resource||Item||Limit (for regular users)||Adjustable|
|Computing||Resource Orchestration Service (ROS) quota||Default: 100.|
|vCPU quota of pay-as-you-go instances||500 vCPU cores|
|High-specification pay-as-you-go instances (with more than 16 vCPU cores)||Unavailable for purchase. Only pay-as-you-go instances with less than 16 vCPU cores can be purchased.|
|vCPU quota of preemptible instances||800 vCPU cores|
|Change the billing method from pay-as-you-go to subscription||Not supported by the following instance families: t1, s1, s2, s3, c1, c2, m1, m2, n1, n2, and e3.|
|Auto Scaling (ESS)||The maximum number of ECS instances in a scaling group is 2,000.|
|Operating system||Nodes that run the following operating systems can be added to an ACK cluster:
|Networking||Maximum number of custom route entries in a route table||48|
|Maximum number of vSwitches in a VPC||24|
|Maximum number of VPCs within an account||10|
|Maximum number of private IP addresses in a VPC||65535||N/A|
|Maximum number of IP addresses that can be added to a basic security group||2000||N/A|
|Maximum number of elastic network interfaces (ENIs)||50000||N/A|
|Maximum number of elastic IP addresses (EIPs) within an account||20|
|Server Load Balancer (SLB)||Maximum number of SLB instances within an account||60|
|Maximum number of backend servers that can be attached to an SLB instance||200||N/A|
|Maximum number of listeners that can be added to an SLB instance||50|
|Maximum number of times that an ECS instance can be added to SLB instances as a backend server||50||N/A|
|Elastic Block Storage (EBS)||Maximum number of pay-as-you-go disks in all regions within an account||The quota is five times the number of ECS instances across all regions. You can create at least 10 pay-as-you-go disks within each account.|
|Maximum capacity of pay-as-you-go disks that are used as data disks within an account||Subject to ECS resource usage, regions, and disk types. You can go to the Privileges & Quotas page in the ECS console to view details. For more information, see View quotas (old version).|
Regions that support ACK
- Asia Pacific
Region City Region ID China (Beijing) Beijing cn-beijing China (Zhangjiakou) Zhangjiakou cn-zhangjiakou China (Hohhot) Hohhot cn-huhehaote China (Ulanqab) Ulanqab cn-wulanchabu China (Hangzhou) Hangzhou cn-hangzhou China (Shanghai) Shanghai cn-shanghai China (Shenzhen) Shenzhen cn-shenzhen China (Heyuan) Heyuan cn-heyuan China (Guangzhou) Guangzhou guangzhou China (Chengdu) Chengdu cn-chengdu China (Hong Kong) Hong Kong cn-hongkong Japan (Tokyo) Tokyo ap-northeast-1 Singapore Singapore ap-southeast-1 Australia (Sydney) Sydney ap-southeast-2 Malaysia (Kuala Lumpur) Kuala Lumpur ap-southeast-3 Indonesia (Jakarta) Jakarta ap-southeast-5
- Europe & Americas
Region City Region ID US (Silicon Valley) Silicon Valley us-west-1 US (Virginia) Virginia us-east-1 UK (London) London eu-west-1 Germany (Frankfurt) Frankfurt eu-central-1
- Middle East and India
Region City Region ID UAE (Dubai) Dubai me-east-1 India (Mumbai) Mumbai ap-south-1