You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: updating/updating_a_cluster/control-plane-only-update.adoc
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ To do: Remove this comment once 4.13 docs are EOL.
14
14
15
15
Due to fundamental Kubernetes design, all {product-title} updates between minor versions must be serialized.
16
16
You must update from {product-title} <4.y> to <4.y+1>, and then to <4.y+2>. You cannot update from {product-title} <4.y> to <4.y+2> directly.
17
-
However, administrators who want to update between two even-numbered minor versions can do so incurring only a single reboot of non-control plane hosts.
17
+
However, administrators who want to update between two even-numbered minor versions can do so incurring only a single reboot of non-control plane hosts.
* xref:../../updating/updating_a_cluster/control-plane-only-update.adoc#updating-control-plane-only-update-console_control-plane-only-update[Performing a Control Plane Only update using the web console]
66
66
* xref:../../updating/updating_a_cluster/control-plane-only-update.adoc#updating-control-plane-only-update-cli_control-plane-only-update[Performing a Control Plane Only update using the CLI]
67
+
* xref:../../virt/updating/upgrading-virt.adoc#virt-preventing-workload-updates-during-control-plane-only-update_upgrading-virt[Preventing workload updates during a Control Plane Only update]
0 commit comments