The OpenShift Container Platform update service is the hosted service that provides over-the-air
updates to both OpenShift Container Platform and Red Hat Enterprise Linux CoreOS (RHCOS). It provides a graph,
or diagram that contain vertices and the edges that connect them, of
component Operators. The edges in the graph show which versions you can safely
update to, and the vertices are update payloads that specify the intended state
of the managed cluster components.
The Cluster Version Operator (CVO) in your cluster checks with the
OpenShift Container Platform update service to see the valid updates and update paths based
on current component versions and information in the graph. When you request an
update, the OpenShift Container Platform CVO uses the release image for that update to
upgrade your cluster. The release artifacts are hosted in Quay as container
To allow the OpenShift Container Platform update service to provide only compatible updates,
a release verification pipeline exists to drive automation. Each release
artifact is verified for compatibility with supported cloud platforms and system
architectures as well as other component packages. After the pipeline confirms
the suitability of a release, the OpenShift Container Platform update service notifies you
that it is available.
Because the update service displays all valid updates, you must not force an update to a version that the update service does not display.
During continuous update mode, two controllers run. One continuously updates
the payload manifests, applies them to the cluster, and outputs the status of
the controlled rollout of the Operators, whether they are available, upgrading,
or failed. The second controller polls the OpenShift Container Platform update service to
determine if updates are available.
Reverting your cluster to a previous version, or a rollback, is not supported.
Only upgrading to a newer version is supported.