// Module included in the following assemblies:
//
// * upgrading/rosa-hcp-upgrading.adoc

:_mod-docs-content-type: CONCEPT
[id="rosa-upgrading-lifecycle-policy_{context}"]
= Life cycle policies and planning

[role="_abstract"]
To plan an upgrade, see the _Red Hat OpenShift Service on AWS update life cycle_ in the "Additional resources" section. 
The life cycle page includes release definitions, support and update requirements, installation policy information and life cycle dates.

Updates are manually initiated or automatically scheduled. Red Hat Site Reliability Engineers (SREs) monitor update progress and remedy any issues encountered.

You can use update channels to decide which {product-title} minor version to update your clusters to. {product-title} supports updates through the `stable-4.y`, `eus-4.y`, and `fast-4.y` channels.

ifdef::openshift-rosa-hcp[]
//The following note should be removed when the entire HCP fleet is confirmed multi-arch
[NOTE]
====
If your control plane is not currently multi-architecture enabled, the update process will first migrate the cluster to a multi-architecture image and then apply the version update. Multi-architecture clusters are capable of running both x86-based and Arm-based workloads. Clusters created after 25 July, 2024 are multi-architecture enabled by default.
====
endif::openshift-rosa-hcp[]
