mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
37 lines
1.6 KiB
Plaintext
37 lines
1.6 KiB
Plaintext
:_mod-docs-content-type: ASSEMBLY
|
|
[id="rosa-upgrading"]
|
|
= Upgrading ROSA Classic clusters
|
|
include::_attributes/attributes-openshift-dedicated.adoc[]
|
|
:context: rosa-upgrading
|
|
|
|
toc::[]
|
|
|
|
[id="rosa-lifecycle-policy_{context}"]
|
|
== Life cycle policies and planning
|
|
|
|
To plan an upgrade, review the xref:../rosa_architecture/rosa_policy_service_definition/rosa-life-cycle.adoc#rosa-life-cycle[{product-title} update life cycle]. The life cycle page includes release definitions, support and upgrade requirements, installation policy information and life cycle dates.
|
|
|
|
Upgrades are manually initiated or automatically scheduled. Red Hat Site Reliability Engineers (SREs) monitor upgrade progress and remedy any issues encountered.
|
|
|
|
[id="rosa-sts-upgrading-a-cluster"]
|
|
== Upgrading a ROSA cluster
|
|
There are three methods to upgrade {product-title} (ROSA) clusters:
|
|
|
|
* Individual upgrades through the ROSA CLI (`rosa`)
|
|
* Individual upgrades through the {cluster-manager-url}
|
|
* Recurring upgrades through the {cluster-manager-url}
|
|
|
|
[NOTE]
|
|
====
|
|
For steps to upgrade a ROSA cluster that uses the AWS Security Token Service (STS), see xref:../upgrading/rosa-upgrading-sts.adoc#rosa-upgrading-sts[Upgrading ROSA clusters with STS].
|
|
====
|
|
|
|
[NOTE]
|
|
====
|
|
When following a scheduled upgrade policy, there might be a delay of an hour or more before the upgrade process begins, even if it is an immediate upgrade. Additionally, the duration of the upgrade might vary based on your workload configuration.
|
|
====
|
|
|
|
include::modules/rosa-upgrading-cli-tutorial.adoc[leveloffset=+2]
|
|
include::modules/rosa-upgrading-manual-ocm.adoc[leveloffset=+2]
|
|
include::modules/rosa-upgrading-automatic-ocm.adoc[leveloffset=+2]
|