Azure Kubernetes 服务 (AKS) 中的配额、虚拟机大小限制和适用地区Quotas, virtual machine size restrictions, and region availability in Azure Kubernetes Service (AKS)

所有 Azure 服务都设置针对资源和功能的默认限制和配额。All Azure services set default limits and quotas for resources and features. 某些虚拟机 (VM) SKU 也被限制使用。Certain virtual machine (VM) SKUs are also restricted for use.

本文详述了 Azure Kubernetes 服务 (AKS) 资源的默认资源限制,以及 Azure 区域中 AKS 的可用性。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

资源Resource 限制Limit
每个订阅的最大群集数Maximum clusters per subscription 100100
包含虚拟机可用性集和基本负载均衡器 SKU 的每个群集的最大节点数Maximum nodes per cluster with Virtual Machine Availability Sets and Basic Load Balancer SKU 100100
包含虚拟机规模集和标准负载均衡器 SKU 的每个群集的最大节点数Maximum nodes per cluster with Virtual Machine Scale Sets and Standard Load Balancer SKU 1000(每个节点池 100 个节点)1000 (100 nodes per node pool)
每个节点的最大 Pod 数:带 Kubenet 的基本网络Maximum pods per node: Basic networking with Kubenet 110110
每个节点的最大 Pod 数:通过 Azure 容器联网界面进行高级联网Maximum pods per node: Advanced networking with Azure Container Networking Interface Azure CLI 部署:301Azure CLI deployment: 301
Azure 资源管理器模板:301Azure Resource Manager template: 301
门户部署:30Portal deployment: 30

1使用 Azure CLI 或资源管理器模板部署 Azure Kubernetes 服务 (AKS) 群集时,此值是可以配置的,最大可以配置为每节点 250 个 Pod。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. 在部署 AKS 群集以后,或者在使用 Azure 门户部署群集的情况下,不能配置每节点的最大 Pod 数。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. 若要了解相关限制,请参阅 Azure 订阅和服务限制For the relevant limits, see Azure subscription and service limits.

重要

升级 AKS 群集时,会临时使用其他资源。When you upgrade an AKS cluster, additional resources are temporarily consumed. 这些资源包括虚拟网络子网中的可用 IP 地址,或者虚拟机 vCPU 配额。These resources include available IP addresses in a virtual network subnet, or virtual machine vCPU quota. 如果使用 Windows Server 容器,则唯一认可的将最新更新应用于节点的方法是执行升级操作。If you use Windows Server containers, the only endorsed approach to apply the latest updates to the nodes is to perform an upgrade operation. 群集升级过程失败可能表明没有可用的 IP 地址空间或 vCPU 配额来处理这些临时资源。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. 有关 Windows Server 节点升级过程的详细信息,请参阅升级 AKS 中的节点池For more information on the Windows Server node upgrade process, see Upgrade a node pool in AKS.

受限制的 VM 大小Restricted VM sizes

AKS 群集中的每个节点都包含固定数量的计算资源,例如 vCPU 和内存。Each node in an AKS cluster contains a fixed amount of compute resources such as vCPU and memory. 如果某个 AKS 节点包含的计算资源不足,则 Pod 可能无法正常运行。If an AKS node contains insufficient compute resources, pods might fail to run correctly. 若要确保所需的 kube-system Pod 和你的应用程序能够可靠地进行计划,请勿在 AKS 中使用以下 VM SKUTo ensure that the required kube-system pods and your applications can reliably be scheduled, don't use the following VM SKUs in AKS:

  • Standard_A0Standard_A0
  • Standard_A1Standard_A1
  • Standard_A1_v2Standard_A1_v2
  • Standard_B1sStandard_B1s
  • Standard_B1msStandard_B1ms
  • Standard_F1Standard_F1
  • Standard_F1sStandard_F1s

有关 VM 类型及其计算资源的详细信息,请参阅 Azure 中的虚拟机的大小For more information on VM types and their compute resources, see Sizes for virtual machines in Azure.

上市区域Region availability

有关可以在其中部署和运行群集的地点的最新列表,请参阅 AKS 适用地区For the latest list of where you can deploy and run clusters, see AKS region availability.

后续步骤Next steps

某些默认限制和配额可以提高。Certain default limits and quotas can be increased. 如果资源支持提高配额,请通过 Azure 支持请求来请求提高配额(请选择“配额”作为“支持类型” )。If your resource supports an increase, request the increase through an Azure support request (for Support type, select Quota).