Skip to content

BZ-1920414: Clarifying the revision numbers are examples #30077

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bergerhoffer merged 1 commit into from
Mar 4, 2021
Merged

BZ-1920414: Clarifying the revision numbers are examples #30077

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 15 additions & 5 deletions modules/dr-restoring-cluster-state.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
+
Expand All @@ -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`:
+
Expand All @@ -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`:
+
Expand All @@ -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.
+
Expand Down
3 changes: 2 additions & 1 deletion modules/nodes-nodes-audit-policy.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down