Skip to content

Commit ef19c4b

Browse files
authored
Merge pull request #78504 from seanmck/windows-snat
Added limitation around Windows node SNAT and basic LB
2 parents c53843f + 344d0ce commit ef19c4b

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/aks/windows-node-limitations.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: tylermsft
66

77
ms.service: container-service
88
ms.topic: article
9-
ms.date: 05/06/2019
9+
ms.date: 05/31/2019
1010
ms.author: twhitney
1111

1212
#Customer intent: As a cluster operator, I want to understand the current limitations when running Windows node pools and application workloads.
@@ -43,6 +43,7 @@ The following upstream limitations for Windows Server containers in Kubernetes a
4343
The following additional limitations apply to Windows Server node pool support in AKS:
4444

4545
- An AKS cluster always contains a Linux node pool as the first node pool. This first Linux-based node pool can't be deleted unless the AKS cluster itself is deleted.
46+
- Currently, AKS only supports the basic load balancer, which only allows for one backend pool, the default Linux node pool. As a result, outbound traffic from Windows pods will always be [translated to an Azure-managed public IP address][azure-outbound-traffic]. Since this IP address is not configurable, it is not currently possible to whitelist traffic coming from Windows pods.
4647
- AKS clusters must use the Azure CNI (advanced) networking model.
4748
- Kubenet (basic) networking is not supported. You can't create an AKS cluster that uses kubenet. For more information on the differences in network models, see [Network concepts for applications in AKS][azure-network-models].
4849
- The Azure CNI network model requires additional planning and considerations for IP address management. For more information on how to plan and implement Azure CNI, see [Configure Azure CNI networking in AKS][configure-azure-cni].
@@ -85,3 +86,4 @@ To get started with Windows Server containers in AKS, [create a node pool that r
8586
[windows-node-cli]: windows-container-cli.md
8687
[aks-support-policies]: support-policies.md
8788
[aks-faq]: faq.md
89+
[azure-outbound-traffic]: ../load-balancer/load-balancer-outbound-connections.md#defaultsnat

0 commit comments

Comments
 (0)