Limits

Overview

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

Quotas of underlying cloud resources

Regions that support ACK