From 59bbc1c61b9404e35cb04fbdcef41fbe77c6ec25 Mon Sep 17 00:00:00 2001 From: Andrea Hoffer Date: Wed, 3 Mar 2021 14:26:57 -0500 Subject: [PATCH] BZ-1920414: Clarifying the revision numbers are examples --- modules/dr-restoring-cluster-state.adoc | 20 +++++++++++++++----- modules/nodes-nodes-audit-policy.adoc | 3 ++- 2 files changed, 17 insertions(+), 6 deletions(-) diff --git a/modules/dr-restoring-cluster-state.adoc b/modules/dr-restoring-cluster-state.adoc index 9d940dd9f1ce..4018ba07a8c3 100644 --- a/modules/dr-restoring-cluster-state.adoc +++ b/modules/dr-restoring-cluster-state.adoc @@ -211,10 +211,11 @@ Review the `NodeInstallerProgressing` status condition for etcd to verify that a [source,terminal] ---- AllNodesAtLatestRevision -3 nodes are at revision 3 +3 nodes are at revision 7 <1> ---- +<1> In this example, the latest revision number is `7`. + -If the output shows a message such as `2 nodes are at revision 3; 1 nodes are at revision 4`, this means that the update is still in progress. Wait a few minutes and try again. +If the output includes multiple revision numbers, such as `2 nodes are at revision 6; 1 nodes are at revision 7`, this means that the update is still in progress. Wait a few minutes and try again. . After etcd is redeployed, force new rollouts for the control plane. The Kubernetes API server will reinstall itself on the other nodes because the kubelet is connected to API servers using an internal load balancer. + @@ -239,8 +240,11 @@ Review the `NodeInstallerProgressing` status condition to verify that all nodes [source,terminal] ---- AllNodesAtLatestRevision -3 nodes are at revision 3 +3 nodes are at revision 7 <1> ---- +<1> In this example, the latest revision number is `7`. ++ +If the output includes multiple revision numbers, such as `2 nodes are at revision 6; 1 nodes are at revision 7`, this means that the update is still in progress. Wait a few minutes and try again. .. Update the `kubecontrollermanager`: + @@ -261,8 +265,11 @@ Review the `NodeInstallerProgressing` status condition to verify that all nodes [source,terminal] ---- AllNodesAtLatestRevision -3 nodes are at revision 3 +3 nodes are at revision 7 <1> ---- +<1> In this example, the latest revision number is `7`. ++ +If the output includes multiple revision numbers, such as `2 nodes are at revision 6; 1 nodes are at revision 7`, this means that the update is still in progress. Wait a few minutes and try again. .. Update the `kubescheduler`: + @@ -283,8 +290,11 @@ Review the `NodeInstallerProgressing` status condition to verify that all nodes [source,terminal] ---- AllNodesAtLatestRevision -3 nodes are at revision 3 +3 nodes are at revision 7 <1> ---- +<1> In this example, the latest revision number is `7`. ++ +If the output includes multiple revision numbers, such as `2 nodes are at revision 6; 1 nodes are at revision 7`, this means that the update is still in progress. Wait a few minutes and try again. . Verify that all master hosts have started and joined the cluster. + diff --git a/modules/nodes-nodes-audit-policy.adoc b/modules/nodes-nodes-audit-policy.adoc index dfef909b3a8b..1f3c7a810321 100644 --- a/modules/nodes-nodes-audit-policy.adoc +++ b/modules/nodes-nodes-audit-policy.adoc @@ -48,8 +48,9 @@ Review the `NodeInstallerProgressing` status condition for the Kubernetes API se [source,terminal] ---- AllNodesAtLatestRevision -3 nodes are at revision 12 +3 nodes are at revision 12 <1> ---- +<1> In this example, the latest revision number is `12`. + If the output shows a message similar to one of the following, this means that the update is still in progress. Wait a few minutes and try again.