diff --git a/doc/source/dist_cloud/kubernetes/distributed-upgrade-orchestration-process-using-the-cli.rst b/doc/source/dist_cloud/kubernetes/distributed-upgrade-orchestration-process-using-the-cli.rst
index b75c336b6..bb6528ca5 100644
--- a/doc/source/dist_cloud/kubernetes/distributed-upgrade-orchestration-process-using-the-cli.rst
+++ b/doc/source/dist_cloud/kubernetes/distributed-upgrade-orchestration-process-using-the-cli.rst
@@ -277,6 +277,13 @@ following conditions:
         | updated_at             | 2020-02-02T14:42:19.376688 |
         +------------------------+----------------------------+
 
+    .. warning::
+        Do not log in to the subcloud using the sysadmin account during an upgrade
+        procedure. During an upgrade, the subcloud password is reset to the default
+        value and is subsequently resynced, and any login attempt during the
+        upgrade will fail. Also, consecutive unsuccessful login attempts may lock
+        your account.
+
 #.  To show the step currently being performed on each of the subclouds, use
     the :command:`dcmanager strategy-step list` command.
 
@@ -328,6 +335,12 @@ the secret payload is, "username: admin password:<password>", see,
 :ref:`Update Docker Registry Credentials on a Subcloud
 <updating-docker-registry-credentials-on-a-subcloud>` for more information.
 
+    .. note::
+        Before attempting to log in to the subclouds using the sysadmin account,
+        verify that the subcloud ``platform_sync_status`` is synced. This would
+        ensure that the sysadmin password is successfully resynced to the subclouds
+        and that login attempts do not fail.
+
 .. only:: partner
 
    .. include:: /_includes/distributed-upgrade-orchestration-process-using-the-cli.rest