Quotas, virtual machine size restrictions, and region availability in Azure Kubernetes Service (AKS)
All Azure services set default limits and quotas for resources and features. Certain virtual machine (VM) SKUs are also restricted for use.
This article details the default resource limits for Azure Kubernetes Service (AKS) resources and the availability of AKS in Azure regions.
Service quotas and limits
|Maximum clusters per subscription||100|
|Maximum nodes per cluster with Virtual Machine Availability Sets and Basic Load Balancer SKU||100|
|Maximum nodes per cluster with Virtual Machine Scale Sets and Standard Load Balancer SKU||800 (100 nodes per node pool)|
|Maximum pods per node: Basic networking with Kubenet||110|
|Maximum pods per node: Advanced networking with Azure Container Networking Interface||Azure CLI deployment: 301
Azure Resource Manager template: 301
Portal deployment: 30
1When you deploy an Azure Kubernetes Service (AKS) cluster with the Azure CLI or a Resource Manager template, this value is configurable up to 250 pods per node. You can't configure maximum pods per node after you've already deployed an AKS cluster, or if you deploy a cluster by using the Azure portal.
All other network, compute, and storage limitations apply to the provisioned infrastructure. For the relevant limits, see Azure subscription and service limits.
When you upgrade an AKS cluster, additional resources are temporarily consumed. These resources include available IP addresses in a virtual network subnet, or virtual machine vCPU quota. If you use Windows Server containers (currently in preview in AKS), the only endorsed approach to apply the latest updates to the nodes is to perform an upgrade operation. A failed cluster upgrade process may indicate that you don't have the available IP address space or vCPU quota to handle these temporary resources. For more information on the Windows Server node upgrade process, see Upgrade a node pool in AKS.
Restricted VM sizes
Each node in an AKS cluster contains a fixed amount of compute resources such as vCPU and memory. If an AKS node contains insufficient compute resources, pods might fail to run correctly. To ensure that the required kube-system pods and your applications can reliably be scheduled, don't use the following VM SKUs in AKS:
For more information on VM types and their compute resources, see Sizes for virtual machines in Azure.
For the latest list of where you can deploy and run clusters, see AKS region availability.
Certain default limits and quotas can be increased. If your resource supports an increase, request the increase through an Azure support request (for Issue type, select Quota).