| title | description | services | author | ms.service | ms.topic | ms.date | ms.author | ms.custom |
|---|---|---|---|---|---|---|---|---|
include file |
include file |
container-service |
mlearned |
container-service |
include |
11/22/2019 |
mlearned |
include file |
| Resource | Limit |
|---|---|
| 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 |
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.