Quotas and region availability for Azure Kubernetes Service (AKS)

All Azure services include certain default limits and quotas for resources and features. The following sections detail the default resource limits for several Azure Kubernetes Service (AKS) resources, as well as the availability of the AKS service in Azure regions.

Service quotas and limits

Resource Default limit
Maximum clusters per subscription 100
Maximum nodes per cluster 100
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 110 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.

Provisioned infrastructure

All other network, compute, and storage limitations apply to the provisioned infrastructure. See Azure subscription and service limits for the relevant limits.

Region availability

Azure Kubernetes Service (AKS) is available in the following regions:

  • Australia East
  • Australia Southeast
  • Canada Central
  • Canada East
  • Central India
  • Central US
  • East Asia
  • East US
  • East US2
  • France Central
  • Japan East
  • Korea Central
  • Korea South
  • North Europe
  • Southeast Asia
  • South Central US
  • South India
  • UK South
  • UK West
  • West Europe
  • West US
  • West US 2

Next steps

Certain default limits and quotas can be increased. To request an increase of one or more resources that support such an increase, submit an Azure support request (select "Quota" for Issue type).