From 0d2091fb5be2c2c823213a8f38f599e978d28960 Mon Sep 17 00:00:00 2001 From: Trapier Marshall Date: Thu, 5 Sep 2019 05:49:53 -0400 Subject: [PATCH] ucp cli upgrade: emphasize run on only one node (#9366) --- ee/ucp/admin/install/upgrade.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ee/ucp/admin/install/upgrade.md b/ee/ucp/admin/install/upgrade.md index c7fe20b8da..1ac191a575 100644 --- a/ee/ucp/admin/install/upgrade.md +++ b/ee/ucp/admin/install/upgrade.md @@ -178,7 +178,7 @@ This is the traditional approach to upgrading UCP and is often used when the order in which UCP worker nodes is upgraded is NOT important. To upgrade UCP, ensure all Docker engines have been upgraded to the -corresponding new version. Then a user should SSH to a UCP manager node and run +corresponding new version. Then a user should SSH to one UCP manager node and run the following command. The upgrade command should not be run on a workstation with a client bundle. @@ -190,6 +190,9 @@ $ docker container run --rm -it \ upgrade \ --interactive ``` + +The upgrade command will print messages regarding the progress of the upgrade as +it automatically upgrades UCP on all nodes in the cluster. ### Phased in-place cluster upgrade