Merge pull request #223731 from allyford/Windows-docs-clean-up-(outbound-nat,-add-windows-nodepool)

Update NAT Gateway, HPC, and Windows Node pools

Author: prmerger-automator[bot]

articles/aks/learn/quick-windows-container-deploy-cli.md

@@ -109,29 +109,49 @@ az aks create \
 
 After a few minutes, the command completes and returns JSON-formatted information about the cluster. Occasionally the cluster can take longer than a few minutes to provision. Allow up to 10 minutes in these cases.
 
+## Add a Windows node pool
+By default, an AKS cluster is created with a node pool that can run Linux containers. Use the `az aks nodepool add` command to add an additional node pool that can run Windows Server containers alongside the Linux node pool.
+
+AKS supports Windows Server 2019 and Windows Server 2022 node pools. For Kubernetes versions "1.25.0" and higher, Windows Server 2022 is the default operating system. For earlier versions, Windows Server 2019 will be the default operating system.
+
+Use the `az aks nodepool add` command to add a Windows nodepool:
+
+```azurecli
+az aks nodepool add \
+    --resource-group myResourceGroup \
+    --cluster-name myAKSCluster \
+    --os-type Windows \
+    --name npwin \
+    --node-count 1
+```
+
+The above command creates a new node pool named *npwin* and adds it to the *myAKSCluster*. The above command also uses the default subnet in the default vnet created when running `az aks create`. The OS SKU was not specified so the nodepool will be set to the default operating system based on the Kubernetes version of the cluster. 
+
+
 ## Add a Windows Server 2019 node pool
 
-By default, an AKS cluster is created with a node pool that can run Linux containers. Use `az aks nodepool add` command to add an additional node pool that can run Windows Server containers alongside the Linux node pool.
+When creating a Windows node pool, the default operating system will be Windows Server 2019 for Kubernetes versions below "1.25.0". To use Windows Server 2019 nodes when not default, you will need to specify an OS SKU type of `Windows2019`.
 
 ```azurecli-interactive
 az aks nodepool add \
     --resource-group myResourceGroup \
     --cluster-name myAKSCluster \
     --os-type Windows \
+    --os-sku Windows2019 \ 
     --name npwin \
     --node-count 1
 ```
 
-The above command creates a new node pool named *npwin* and adds it to the *myAKSCluster*. The above command also uses the default subnet in the default vnet created when running `az aks create`.
+The above command creates a new Windows Server 2019 node pool named *npwin* and adds it to the *myAKSCluster*. The above command also uses the default subnet in the default vnet created when running `az aks create`. 
 
 ## Add a Windows Server 2022 node pool
 
-When creating a Windows node pool, the default operating system will be Windows Server 2019. To use Windows Server 2022 nodes, you will need to specify an OS SKU type of `Windows2022`.
+When creating a Windows node pool, the default operating system will be Windows Server 2022 for Kubernetes versions "1.25.0" and higher. To use Windows Server 2022 nodes when not default, you will need to specify an OS SKU type of `Windows2022`.
 
 > [!NOTE]
 > Windows Server 2022 requires Kubernetes version "1.23.0" or higher.
 
-Use `az aks nodepool add` command to add a Windows Server 2022 node pool:
+Use the `az aks nodepool add` command to add a Windows Server 2022 node pool:
 
 ```azurecli
 az aks nodepool add \

articles/aks/nat-gateway.md

@@ -133,7 +133,7 @@ To create an AKS cluster with a user-assigned NAT Gateway, use `--outbound-type
         --assign-identity $IDENTITY_ID
     ```
 
-## Disable OutboundNAT for Windows
+## Disable OutboundNAT for Windows (preview)
 
 Windows OutboundNAT can cause certain connection and communication issues with your AKS pods. Some of these issues include:
 
@@ -143,6 +143,9 @@ Windows OutboundNAT can cause certain connection and communication issues with y
 
 Windows enables OutboundNAT by default. You can now manually disable OutboundNAT when creating new Windows agent pools.
 
+> [!NOTE]
+> OutboundNAT can only be disabled on Windows Server 2019 nodepools.
+
 ### Prerequisites
 
 * You need to use `aks-preview` and register the feature flag.

articles/aks/use-windows-hpc.md

@@ -71,7 +71,6 @@ spec:
         - name: powershell
           image: mcr.microsoft.com/powershell:lts-nanoserver-1809
           securityContext:
-            privileged: true
             windowsOptions:
               hostProcess: true
               runAsUserName: "NT AUTHORITY\\SYSTEM"