rackpause strategy documentation

Author: vivekjMSFT

articles/operator-nexus/howto-cluster-runtime-upgrade-with-pauserack-strategy.md

@@ -18,22 +18,21 @@ This how-to guide explains the steps to execute a cluster runtime upgrade with p
 Please follow the steps mentioned in prerequistie section of [Upgrading cluster runtime from Azure CLI](./howto-cluster-runtime-upgrade.md)
 
 > **Note:**
-> Upgrades with the Rack Pause strategy will only work after the management bundle (CMBU) has been upgraded to 3.8 or greater.
+> Upgrades with the PauseRack strategy is available starting  API version 2024-06-01-preview.
 
 ## Procedure
 
 1. Enable Rack Pause upgrade strategy on a Nexus cluster
 
     > **Note:**
-    > choose threshold value as desired.
+    > Below is just a reference command, please choose threshold values as desired.
 
     Example:
 
     ```azurecli
     az networkcloud cluster update --name "clusterName" --resource-group "resourceGroupName" --update-strategy \
         strategy-type="PauseRack" \
-        wait-time-minutes=0 \
-        <threshold values as desired>
+        wait-time-minutes=0
     ```
 
 2. Confirm that the cluster resource JSON in the JSON View reflects the rack pause upgrade strategy.

articles/operator-nexus/howto-cluster-runtime-upgrade.md

@@ -123,6 +123,12 @@ Upon successful execution of the command, the updateStrategy values specified wi
       "waitTimeMinutes": 15,
     },
 ```
+> [!WARNING]
+> When a threshold value below 100% is set, it’s possible that any unhealthy nodes might not be upgraded, yet the “Cluster” status could still indicate that upgrade was sucessfull. For troubleshooting issues with bare metal machines, please refer to the troubleshooting guide titled [Troubleshoot Azure Operator Nexus server problems](troubleshoot-reboot-reimage-replace.md)
+
+## Upgrade with PauseRack Strategy
+
+Starting with API version 2024-06-01-preview, runtime upgrades can be triggered using a "PauseRack" strategy. When you execute a cluster runtime upgrade with the PauseRack" strategy, it will update one rack at a time in the cluster and then pause, awaiting confirmation before proceeding to the next rack. All existing thresholds will continue to be respected with the "PauseRack" strategy. To carry out a cluster runtime upgrade using the "PauseRack" strategy, please follow the steps outlined in [Upgrading cluster runtime with a pause rack strategy](howto-cluster-runtime-upgrade-with-pauserack-strategy.md)
 
 ## Frequently Asked Questions