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, including usage restrictions for certain virtual machine (VM) SKUs.
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||1000|
|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||1000 (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
|Open Service Mesh (OSM) AKS addon preview||Kubernetes Cluster Version: 1.19+2
OSM controllers per cluster: 12
Pods per OSM controller: 5002
Kubernetes service accounts managed by OSM: 502
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.
2The OSM add-on for AKS is in a preview state and will undergo additional enhancements prior to general availability (GA). During the preview phase it is recommended to not surpass the limits shown.
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, extra resources are temporarily consumed. These resources include include available IP addresses in a virtual network subnet or virtual machine vCPU quota.
For Windows Server containers, you can perform an upgrade operation to apply the latest node updates. If you don't have the available IP address space or vCPU quota to handle these temporary resources, the cluster upgrade process will fail. 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 the required kube-system pods and your applications can be reliably 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.
You can increase certain default limits and quotas. If your resource supports an increase, request the increase through an Azure support request (for Issue type, select Quota).