You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/aks/windows-vs-linux-containers.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,10 +3,9 @@ title: Windows container considerations in Azure Kubernetes Service
3
3
titleSuffix: Azure Kubernetes Service
4
4
description: See the Windows container considerations with Azure Kubernetes Service (AKS).
5
5
ms.topic: article
6
-
ms.date: 12/13/2023
6
+
ms.date: 01/12/2024
7
7
ms.author: schaffererin
8
8
author: schaffererin
9
-
10
9
---
11
10
12
11
# Windows container considerations with Azure Kubernetes Service
@@ -28,7 +27,7 @@ This article covers important considerations to keep in mind when using Windows
28
27
29
28
| Feature | Windows considerations |
30
29
|-----------|:-----------|
31
-
|[Cluster creation][cluster-configuration]| • The first system node pool *must* be Linux.<br/> • AKS Windows clusters have a maximum limit of 10 node pools.<br/> • AKS Windows clusters have a maximum limit of 100 nodes in each node pool.<br/> • The Windows Server node pool name has a limit of six characters. |
30
+
|[Cluster creation][cluster-configuration]| • The first system node pool *must* be Linux.<br/> • The maximum number of nodes per cluster is 5000.<br/> • The Windows Server node pool name has a limit of six characters. |
32
31
|[Privileged containers][privileged-containers]| Not supported. The equivalent is **HostProcess Containers (HPC) containers**. |
33
32
|[HPC containers][hpc-containers]| • HostProcess containers are the Windows alternative to Linux privileged containers. For more information, see [Create a Windows HostProcess pod](https://kubernetes.io/docs/tasks/configure-pod-container/create-hostprocess-pod/). |
34
33
|[Azure Network Policy Manager (Azure)][azure-network-policy]| Azure Network Policy Manager doesn't support:<br/> • Named ports<br/> • SCTP protocol<br/> • Negative match labels or namespace selectors (all labels except "debug=true")<br/> • "except" CIDR blocks (a CIDR with exceptions)<br/> • Windows Server 2019<br/> |
| Maximum clusters per subscription | 5000 <br />Note: spread clusters across different regions to account for Azure API throttling limits|
15
-
| Maximum nodes per cluster with Virtual Machine Scale Sets and [Standard Load Balancer SKU][standard-load-balancer]| 5000 across all [node-pools][node-pool] (default limit: 1000) <br />Note: Running more than a 1000 nodes per cluster requires increasing the default node limit quota. [Contact support][Contact Support] for assistance.|
16
-
|Maximum nodes per node pool (Virtual Machine Scale Sets node pools) | 1000|
| Maximum pods per node: with [Azure Container Networking Interface][Azure CNI]| Maximum: 250 <br /> Default: 30 |
20
-
| Open Service Mesh (OSM) AKS addon | Kubernetes Cluster Version: AKS Supported Versions<br />OSM controllers per cluster: 1<br />Pods per OSM controller: 1600<br />Kubernetes service accounts managed by OSM: 160 |
21
-
|Maximum load-balanced kubernetes services per cluster with [Standard Load Balancer SKU][standard-load-balancer]|300 |
22
-
| Maximum nodes per cluster with Virtual Machine Availability Sets and Basic Load Balancer SKU | 100|
| Standard tier | Automatically scales Kubernetes API server based on load. Larger control plane component limits and API server/etc instances.|
29
-
| Free tier | Limited resources with [inflight requests limit](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/) of 50 mutating and 100 read-only calls. Recommended node limit of 10 nodes per cluster. Best for experimenting, learning, and simple testing. **Not advised for production/critical workloads**.|
12
+
| Resource | Limit |
13
+
|--|:-|
14
+
| Maximum clusters per subscription | 5000 <br />Note: spread clusters across different regions to account for Azure API throttling limits |
15
+
| Maximum nodes per cluster with Virtual Machine Scale Sets and [Standard Load Balancer SKU][standard-load-balancer]| 5000 across all [node-pools][node-pool] (default limit: 1000) <br />Note: Running more than a 1000 nodes per cluster requires increasing the default node limit quota. [Contact support][Contact Support] for assistance.|
16
+
|Maximum nodes per node pool (Virtual Machine Scale Sets node pools) | 1000 |
| Maximum pods per node: with [Azure Container Networking Interface (Azure CNI)][Azure CNI]<sup>1</sup> | Maximum: 250 <br /> Maximum recommended for Windows Server containers: 110 <br /> Default: 30|
20
+
| Open Service Mesh (OSM) AKS addon | Kubernetes Cluster Version: AKS Supported Versions<br />OSM controllers per cluster: 1<br />Pods per OSM controller: 1600<br />Kubernetes service accounts managed by OSM: 160 |
21
+
|Maximum load-balanced kubernetes services per cluster with [Standard Load Balancer SKU][standard-load-balancer]| 300|
22
+
| Maximum nodes per cluster with Virtual Machine Availability Sets and Basic Load Balancer SKU | 100 |
23
+
24
+
<sup>1</sup> Windows Server containers must use Azure CNI networking plug-in. Kubenet is not supported for Windows Server containers.
25
+
26
+
| Kubernetes Control Plane tier | Limit |
27
+
|--|:-|
28
+
| Standard tier | Automatically scales Kubernetes API server based on load. Larger control plane component limits and API server/etc instances. |
29
+
| Free tier | Limited resources with [inflight requests limit](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/) of 50 mutating and 100 read-only calls. Recommended node limit of 10 nodes per cluster. Best for experimenting, learning, and simple testing. **Not advised for production/critical workloads**. |
0 commit comments