Skip to content

[enterprise-4.21] OCPBUGS#64614 Formatting changes in updating a cluster by using the cli #102158

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
merged 1 commit into from
Nov 10, 2025
+7 −7
Merged

[enterprise-4.21] OCPBUGS#64614 Formatting changes in updating a cluster by using the cli #102158

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
14 changes: 7 additions & 7 deletions modules/update-upgrading-cli.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,7 @@ endif::openshift-origin[]
+
[source,terminal]
----
$ oc adm upgrade --to-latest=true <1>
$ oc adm upgrade --to-latest=true
----

** To update to a specific version:
Expand All @@ -125,17 +125,17 @@ $ oc adm upgrade --to=<version> <1>
<1> `<version>` is the update version that you obtained from the output of the
`oc adm upgrade recommend` command.
+
.. If the cluster administrator evaluates the potential known risks and decides it is acceptable for the current cluster, then the administrator can waive the safety guards and proceed with the update by running the following command:
[IMPORTANT]
====
When using `oc adm upgrade --help`, there is a listed option for `--force`. This is _heavily discouraged_, because using the `--force` option bypasses cluster-side guards, including release verification and precondition checks. Using `--force` does not guarantee a successful update. Bypassing guards puts the cluster at risk.
====
+
. If the cluster administrator evaluates the potential known risks and decides it is acceptable for the current cluster, then the administrator can waive the safety guards and proceed with the update by running the following command:
+
[source,terminal]
----
$ oc adm upgrade --allow-not-recommended --to <version>
----
+
[IMPORTANT]
====
When using `oc adm upgrade --help`, there is a listed option for `--force`. This is *heavily discouraged*, as using the `--force` option bypasses cluster-side guards, including release verification and precondition checks. Using `--force` does not guarantee a successful update. Bypassing guards put the cluster at risk.
====

. Optional: Review the status of the Cluster Version Operator by running the following command:
+
Expand Down