Update how we upgrade cluster (github#21484)

Z-byte-prog · Sep 14, 2021 · b5cce0c · b5cce0c
1 parent e5742ee
commit b5cce0c
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md b/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md
@@ -79,5 +79,7 @@ Run the `ghe-upgrade` command, providing the package file name you downloaded in
   > gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
   > gpg: Good signature from "GitHub Enterprise (Upgrade Package Key) > <[email protected]>"
   ```
-5. The upgrade process will reboot the primary MySQL node once it completes. Verify that you can `ping` each node after it reboots.
-6. Exit maintenance mode from the administrative shell of any node by running `ghe-cluster-maintenance -u`.
+5. The upgrade process will reboot the primary MySQL node once it completes. Verify that you can `ping` each node after it reboots.{% ifversion ghes > 2.22 %}
+6. Connect to the administrative shell of the primary MySQL node and run the `ghe-cluster-config-apply` command.
+7. When `ghe-cluster-config-apply` is complete, check that the services are in a healthy state by running `ghe-cluster-status`.{% endif %}
+8. Exit maintenance mode from the administrative shell of any node by running `ghe-cluster-maintenance -u`.