[AKS] added label and taint details for spot node pools

Author: zr-msft

articles/aks/spot-node-pool.md

@@ -85,7 +85,8 @@ The following limitations apply when you create and manage AKS clusters with a s
 * A spot node pool must use Virtual Machine Scale Sets.
 * You cannot change ScaleSetPriority or SpotMaxPrice after creation.
 * When setting SpotMaxPrice, the value must be -1 or a positive value with up to five decimal places.
-* A spot node pool will have the label *scalesetpriority:spot*, the taint *scalesetpriority=spot:NoSchedule*, and system pods will have anti-affinity.
+* A spot node pool will have the label *kubernetes.azure.com/scalesetpriority:spot*, the taint *kubernetes.azure.com/scalesetpriority=spot:NoSchedule*, and system pods will have anti-affinity.
+* You must add a [corresponding toleration][spot-toleration] to schedule workloads on a spot node pool.
 
 ## Add a spot node pool to an AKS cluster
 
@@ -111,7 +112,7 @@ By default, you create a node pool with a *priority* of *Regular* in your AKS cl
 The command also enables the [cluster autoscaler][cluster-autoscaler], which is recommended to use with spot node pools. Based on the workloads running in your cluster, the cluster autoscaler scales up and scales down the number of nodes in the node pool. For spot node pools, the cluster autoscaler will scale up the number of nodes after an eviction if additional nodes are still needed. If you change the maximum number of nodes a node pool can have, you also need to adjust the `maxCount` value associated with the cluster autoscaler. If you do not use a cluster autoscaler, upon eviction, the spot pool will eventually decrease to zero and require a manual operation to receive any additional spot nodes.
 
 > [!Important]
-> Only schedule workloads on spot node pools that can handle interruptions, such as batch processing jobs and testing environments. It is recommended that you set up [taints and tolerations][taints-tolerations] on your spot node pool to ensure that only workloads that can handle node evictions are scheduled on a spot node pool. For example, the above command ny default adds a taint of *scalesetpriority=spot:NoSchedule* so only pods with a corresponding toleration are scheduled on this node.
+> Only schedule workloads on spot node pools that can handle interruptions, such as batch processing jobs and testing environments. It is recommended that you set up [taints and tolerations][taints-tolerations] on your spot node pool to ensure that only workloads that can handle node evictions are scheduled on a spot node pool. For example, the above command ny default adds a taint of *kubernetes.azure.com/scalesetpriority=spot:NoSchedule* so only pods with a corresponding toleration are scheduled on this node.
 
 ## Verify the spot node pool
 
@@ -123,14 +124,14 @@ az aks nodepool show --resource-group myResourceGroup --cluster-name myAKSCluste
 
 Confirm *scaleSetPriority* is *Spot*.
 
-To schedule a pod to run on a spot node, add a toleration that corresponds to the taint applied to your spot node. The following example shows a portion of a yaml file that defines a toleration that corresponds to a *scalesetpriority=spot:NoSchedule* taint used in the previous step.
+To schedule a pod to run on a spot node, add a toleration that corresponds to the taint applied to your spot node. The following example shows a portion of a yaml file that defines a toleration that corresponds to a *kubernetes.azure.com/scalesetpriority=spot:NoSchedule* taint used in the previous step.
 
 ```yaml
 spec:
   containers:
   - name: spot-example
   tolerations:
-  - key: "scalesetpriority"
+  - key: "kubernetes.azure.com/scalesetpriority"
     operator: "Equal"
     value: "spot"
     effect: "NoSchedule"
@@ -169,6 +170,7 @@ In this article, you learned how to add a spot node pool to an AKS cluster. For
 [pricing-linux]: https://azure.microsoft.com/pricing/details/virtual-machine-scale-sets/linux/
 [pricing-spot]: ../virtual-machine-scale-sets/use-spot.md#pricing
 [pricing-windows]: https://azure.microsoft.com/pricing/details/virtual-machine-scale-sets/windows/
+[spot-toleration]: #verify-the-spot-node-pool
 [taints-tolerations]: operator-best-practices-advanced-scheduler.md#provide-dedicated-nodes-using-taints-and-tolerations
 [use-multiple-node-pools]: use-multiple-node-pools.md
 [vmss-spot]: ../virtual-machine-scale-sets/use-spot.md