Merge pull request #113343 from mlearned/mdl-1527819-pip-per-agent

Mdl 1527819 pip per agent

Author: v-albemi

articles/aks/use-multiple-node-pools.md

@@ -718,22 +718,65 @@ az group deployment create \
 
 It may take a few minutes to update your AKS cluster depending on the node pool settings and operations you define in your Resource Manager template.
 
-## Assign a public IP per node for a node pool (preview)
+## Assign a public IP per node for your node pools (preview)
 
 > [!WARNING]
-> During the preview of assigning a public IP per node, it cannot be used with the *Standard Load Balancer SKU in AKS* due to possible load balancer rules conflicting with VM provisioning. As a result of this limitation, Windows agent pools are not supported with this preview feature. While in preview you must use the *Basic Load Balancer SKU* if you need to assign a public IP per node.
+> You must install the CLI preview extension 0.4.43 or greater to use the public IP per node feature.
 
-AKS nodes do not require their own public IP addresses for communication. However, scenarios may require nodes in a node pool to receive their own dedicated public IP addresses. An common scenario is for gaming workloads, where a console needs to make a direct connection to a cloud virtual machine to minimize hops. This scenario can be achieved on AKS by registering for a preview feature, Node Public IP (preview).
+AKS nodes do not require their own public IP addresses for communication. However, scenarios may require nodes in a node pool to receive their own dedicated public IP addresses. A common scenario is for gaming workloads, where a console needs to make a direct connection to a cloud virtual machine to minimize hops. This scenario can be achieved on AKS by registering for a preview feature, Node Public IP (preview).
 
-Register for the Node Public IP feature by issuing the following Azure CLI command.
+To install and update the latest aks-preview extension, use the following Azure CLI commands:
+
+```azurecli
+az extension add --name aks-preview
+az extension update --name aks-preview
+az extension list
+```
+
+Register for the Node Public IP feature with the following Azure CLI command:
 
 ```azurecli-interactive
 az feature register --name NodePublicIPPreview --namespace Microsoft.ContainerService
 ```
+It may take several minutes for the feature to register.  You can check the status with the following command:
+
+```azurecli-interactive
+ az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/NodePublicIPPreview')].{Name:name,State:properties.state}"
+```
+
+After successful registration, create a new resource group.
+
+```azurecli-interactive
+az group create --name myResourceGroup2 --location eastus
+```
+
+Create a new AKS cluster and attach a public IP for your nodes. Each of the nodes in the node pool receives a unique public IP. You can verify this by looking at the Virtual Machine Scale Set instances.
+
+```azurecli-interactive
+az aks create -g MyResourceGroup2 -n MyManagedCluster -l eastus  --enable-node-public-ip
+```
 
-After successful registration, deploy an Azure Resource Manager template following the same instructions as [above](#manage-node-pools-using-a-resource-manager-template) and add the boolean property `enableNodePublicIP` to agentPoolProfiles. Set the value to `true` as by default it is set as `false` if not specified. 
+For existing AKS clusters, you can also add a new node pool, and attach a public IP for your nodes.
 
-This property is a create-time only property and requires a minimum API version of 2019-06-01. This can be applied to both Linux and Windows node pools.
+```azurecli-interactive
+az aks nodepool add -g MyResourceGroup2 --cluster-name MyManagedCluster -n nodepool2 --enable-node-public-ip
+```
+
+> [!Important]
+> During preview, the Azure Instance Metadata Service doesn't currently support retrieval of public IP addresses for the standard tier VM SKU. Due to this limitation, you can't use kubectl commands to display the public IPs assigned to the nodes. However, the IPs are assigned and function as intended. The public IPs for your nodes are attached to the instances in your Virtual Machine Scale Set.
+
+You can locate the public IPs for your nodes in various ways:
+
+* Use the Azure CLI command [az vmss list-instance-public-ips][az-list-ips]
+* Use [PowerShell or Bash commands][vmss-commands]. 
+* You can also view the public IPs in the Azure portal by viewing the instances in the Virtual Machine Scale Set.
+
+> [!Important]
+> The [node resource group][node-resource-group] contains the nodes and their public IPs. Use the node resource group when executing commands to find the public IPs for your nodes.
+
+```azurecli
+az vmss list-instance-public-ips -g MC_MyResourceGroup2_MyManagedCluster_eastus -n YourVirtualMachineScaleSetName
+```
 
 ## Clean up resources
 
@@ -751,6 +794,12 @@ To delete the cluster itself, use the [az group delete][az-group-delete] command
 az group delete --name myResourceGroup --yes --no-wait
 ```
 
+You can also delete the additional cluster you created for the public IP for node pools scenario.
+
+```azurecli-interactive
+az group delete --name myResourceGroup2 --yes --no-wait
+```
+
 ## Next steps
 
 Learn more about [system node pools][use-system-pool].
@@ -791,3 +840,7 @@ To create and use Windows Server container node pools, see [Create a Windows Ser
 [taints-tolerations]: operator-best-practices-advanced-scheduler.md#provide-dedicated-nodes-using-taints-and-tolerations
 [vm-sizes]: ../virtual-machines/linux/sizes.md
 [use-system-pool]: use-system-pools.md
+[ip-limitations]: ../virtual-network/virtual-network-ip-addresses-overview-arm#standard
+[node-resource-group]: faq.md#why-are-two-resource-groups-created-with-aks
+[vmss-commands]: ../virtual-machine-scale-sets/virtual-machine-scale-sets-networking.md#public-ipv4-per-virtual-machine
+[az-list-ips]: /cli/azure/vmss?view=azure-cli-latest.md#az-vmss-list-instance-public-ips