1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00

OSDOCS-16580

This commit is contained in:
Janelle Neczypor
2025-11-20 15:56:13 -08:00
committed by openshift-cherrypick-robot
parent dd92aac325
commit f7776a159a
4 changed files with 19 additions and 11 deletions

View File

@@ -2,8 +2,7 @@
[id="rosa-upgrade-options_{context}"]
= Upgrade options for {product-title} clusters
In OpenShift, upgrading means provisioning a new component with updated software and using it to replace an existing component that has outdated software.
[role="_abstract"]
You can control the impact of upgrades to your workload by controlling which parts of the cluster are upgraded, for example:
Upgrade only the hosted control plane:: This initiates upgrade of the hosted control plane. It does not impact your worker nodes.

View File

@@ -10,6 +10,7 @@
ifeval::["{context}" != "rosa-hcp-upgrading-whole-cluster"]
= Upgrading the hosted control plane with the ROSA CLI
[role="_abstract"]
You can manually upgrade the hosted control plane of a {product-title} cluster by using the ROSA CLI. This method schedules the control plane for an upgrade if a more recent version is available, either immediately, or at a specified future time.
[NOTE]
@@ -40,9 +41,9 @@ endif::[]
+
[source,terminal]
----
$ rosa describe cluster --cluster=<cluster_name_or_id> <1>
$ rosa describe cluster --cluster=<cluster_name_or_id>
----
<1> Replace `<cluster_name_or_id>` with the cluster name or the cluster ID.
Replace `<cluster_name_or_id>` with the cluster name or the cluster ID.
. List the versions that you can upgrade your control plane to by running the following command:
+
@@ -53,7 +54,7 @@ $ rosa list upgrade --cluster=<cluster_name_or_id>
+
The command returns a list of available updates, including the recommended version.
+
.Example output
*Example output*
+
[source,terminal]
----

View File

@@ -10,6 +10,7 @@
ifeval::["{context}" != "rosa-hcp-upgrading-whole-cluster"]
= Upgrading machine pools with the ROSA CLI
[role="_abstract"]
You can manually upgrade one or more machine pools in a {hcp-title} cluster by using the ROSA CLI. This method schedules the specified machine pool for an upgrade if a more recent version is available, either immediately, or at a specified future time.
[NOTE]
@@ -41,19 +42,22 @@ Machine pool configurations such as node drain timeout, max-unavailable, and max
+
[source,terminal]
----
$ rosa describe cluster --cluster=<cluster_name_or_id> <1>
$ rosa describe cluster --cluster=<cluster_name_or_id>
----
<1> Replace `<cluster_name_or_id>` with the cluster name or the cluster ID.
Replace `<cluster_name_or_id>` with the cluster name or the cluster ID.
+
ifeval::["{context}" != "rosa-hcp-upgrading-whole-cluster"]
.Example output
*Example output*
+
[source,terminal]
----
OpenShift Version: 4.14.0
----
endif::[]
ifeval::["{context}" == "rosa-hcp-upgrading-whole-cluster"]
.Example output
*Example output*
+
[source,terminal]
----
OpenShift Version: 4.14.8
@@ -70,7 +74,7 @@ $ rosa list upgrade --cluster <cluster-name> --machinepool <machinepool_name>
+
The command returns a list of available updates, including the recommended version.
+
.Example output
*Example output*
+
[source,terminal]
----
@@ -93,7 +97,8 @@ Do not upgrade your machine pool to a version higher than your control plane. If
$ rosa describe machinepool --cluster=<cluster_name_or_id> <machinepool_name>
----
+
.Example output
*Example output*
+
[source,terminal]
----
Replicas: 5

View File

@@ -6,6 +6,9 @@ include::_attributes/attributes-openshift-dedicated.adoc[]
toc::[]
[role="_abstract"]
In {product-title}, upgrading provisions a new component with updated software and uses it to replace an existing component that has outdated software.
include::modules/rosa-hcp-upgrade-options.adoc[leveloffset=+1]
.Additional resources