:_mod-docs-content-type: ASSEMBLY
[id="core-cluster-upgrades-eus"]
= Complete an EUS-to-EUS cluster update with {cgu-operator}
include::_attributes/common-attributes.adoc[]
:context: core-cluster-upgrades-eus

toc::[]

[role="_abstract"]
You can partially skip intermediate odd-numbered releases by using control-plane-only EUS-to-EUS updates with {rh-rhacm} policies and {cgu-operator-full} ({cgu-operator}).
With this approach, you can manage control plane and worker version skew during staged rollouts.

include::modules/core-cluster-upgrade-eus-control-plane-only.adoc[leveloffset=+1]

[id="additional-resources_core-cluster-upgrades-eus"]
[role="_additional-resources"]
== Additional resources

* xref:../../../post_installation_configuration/day_2_core_cnf_clusters/updating/update-rhacm-talm-preparing-policies.adoc#core-cluster-upgrades-preparing-policies[Prepare {rh-rhacm} policies and {cgu-operator} for cluster updates]
* xref:../../../post_installation_configuration/day_2_core_cnf_clusters/updating/update-rhacm-talm-worker-management.adoc#core-cluster-upgrades-worker-management[Manage worker nodes during a cluster update with {cgu-operator}]
* xref:../../../post_installation_configuration/day_2_core_cnf_clusters/updating/update-rhacm-talm-health-checks.adoc#core-cluster-upgrades-health-checks[Perform health checks before a cluster update with {cgu-operator}]
* link:https://docs.redhat.com/en/documentation/openshift_container_platform/[{product-title} update documentation]
* link:https://access.redhat.com/support/policy/updates/openshift[{product-title} update lifecycle and support policy]
