Merge pull request #290802 from matternst7258/matternst7258/upgrade-link

[operator-nexus] Adds link to execute runtime upgrade

Author: prmerger-automator[bot]

articles/operator-nexus/concepts-cluster-upgrade-overview.md

@@ -41,6 +41,8 @@ The runtime upgrade starts by upgrading the three management servers designated
 
 Once all management servers are upgraded, the upgrade progresses to the compute servers. Each rack is upgraded in alphanumeric order, and there are various configurations customers can use to dictate how the computes are upgrade to best limit disruption. As each rack progresses, there are various health checks performed in order to ensure the release successfully upgrades and a sufficient number of computes in a rack returns to operational status. When a rack completes, a customer defined waits time starts to provide extra time for workloads to come online. Once each rack upgrades, the upgrade completes and the cluster returns to `Running` status. 
 
+The steps to run a cluster runtime upgrade is located [here](./howto-cluster-runtime-upgrade.md).
+
 ## Runtime upgrade strategies
 
 Each of the strategies explained provide users various controls for how and when compute racks are upgraded. These values are applicable only to the compute servers and not the management servers. Each strategy uses a `thresholdType` and `thresholdValue` to define the number or percent of successfully upgraded compute servers in a rack before proceeding to the next rack.