Skip to content

Latest commit

 

History

History
60 lines (42 loc) · 3.65 KB

understanding-update-channels-release.adoc

File metadata and controls

60 lines (42 loc) · 3.65 KB

Understanding update channels and releases

Update channels are the mechanism by which users declare the {product-title} minor version they intend to update their clusters to. They also allow users to choose the timing and level of support their updates will have through the fast, stable, candidate, and eus channel options. The Cluster Version Operator uses an update graph based on the channel declaration, along with other conditional information, to provide a list of recommended and conditional updates available to the cluster.

Update channels correspond to a minor version of {product-title}. The version number in the channel represents the target minor version that the cluster will eventually be updated to, even if it is higher than the cluster’s current minor version.

For instance, {product-title} 4.10 update channels provide the following recommendations:

  • Updates within 4.10.

  • Updates within 4.9.

  • Updates from 4.9 to 4.10, allowing all 4.9 clusters to eventually update to 4.10, even if they do not immediately meet the minimum z-stream version requirements.

  • eus-4.10 only: updates within 4.8.

  • eus-4.10 only: updates from 4.8 to 4.9 to 4.10, allowing all 4.8 clusters to eventually update to 4.10.

4.10 update channels do not recommend updates to 4.11 or later releases. This strategy ensures that administrators must explicitly decide to update to the next minor version of {product-title}.

Update channels control only release selection and do not impact the version of the cluster that you install. The openshift-install binary file for a specific version of {product-title} always installs that version.

{product-title} {product-version} offers the following update channels:

  • stable-{product-version}

  • eus-4.y (only offered for EUS versions and meant to facilitate updates between EUS versions)

  • fast-{product-version}

  • candidate-{product-version}

If you do not want the Cluster Version Operator to fetch available updates from the update recommendation service, you can use the oc adm upgrade channel command in the OpenShift CLI to configure an empty channel. This configuration can be helpful if, for example, a cluster has restricted network access and there is no local, reachable update recommendation service.

Warning

Red Hat recommends updating to versions suggested by OpenShift Update Service only. For a minor version update, versions must be contiguous. Red Hat does not test updates to noncontiguous versions and cannot guarantee compatibility with earlier versions.