Skip to content

Commit 5eef640

Browse files
authored
Merge pull request #41135 from tmalove/osdocs-2720
[OSDOCS-2720]: Remove backup safety net message from previous release
2 parents 2e2f626 + 52aa716 commit 5eef640

File tree

1 file changed

+0
-8
lines changed

1 file changed

+0
-8
lines changed

updating/updating-cluster-within-minor.adoc

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -18,14 +18,6 @@ Use the web console or `oc adm upgrade channel _<channel>_` to change the update
1818
* Have access to the cluster as a user with `admin` privileges.
1919
See xref:../authentication/using-rbac.adoc[Using RBAC to define and apply permissions].
2020
* Have a recent xref:../backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.adoc#backup-etcd[etcd backup] in case your upgrade fails and you must xref:../backup_and_restore/control_plane_backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.adoc#dr-restoring-cluster-state[restore your cluster to a previous state].
21-
+
22-
{product-title} 4.9 requires an upgrade from etcd version 3.4 to 3.5. If the etcd Operator halts the upgrade, an alert is triggered. To clear this alert, cancel the update with the following command:
23-
+
24-
[source,terminal]
25-
----
26-
$ oc adm upgrade --clear
27-
----
28-
2921
* Ensure all Operators previously installed through Operator Lifecycle Manager (OLM) are updated to their latest version in their latest channel. Updating the Operators ensures they have a valid upgrade path when the default OperatorHub catalogs switch from the current minor version to the next during a cluster upgrade. See xref:../operators/admin/olm-upgrading-operators.adoc#olm-upgrading-operators[Upgrading installed Operators] for more information.
3022
* Ensure that all machine config pools (MCPs) are running and not paused. Nodes associated with a paused MCP are skipped during the update process. You can pause the MCPs if you are performing a canary rollout update strategy.
3123
* If your cluster uses manually maintained credentials, ensure that the Cloud Credential Operator (CCO) is in an upgradeable state. For more information, see _Upgrading clusters with manually maintained credentials_ for xref:../installing/installing_aws/manually-creating-iam.adoc#manually-maintained-credentials-upgrade_manually-creating-iam-aws[AWS], xref:../installing/installing_azure/manually-creating-iam-azure.adoc#manually-maintained-credentials-upgrade_manually-creating-iam-azure[Azure], or xref:../installing/installing_gcp/manually-creating-iam-gcp.adoc#manually-maintained-credentials-upgrade_manually-creating-iam-gcp[GCP].

0 commit comments

Comments
 (0)