EUS-to-EUS update: OpenShift 4.14 -> 4.16

Disclaimer: Links contained herein to external website(s) are provided for convenience only. Red Hat has not reviewed the links and is not responsible for the content or its availability. The inclusion of any link to an external website does not imply endorsement by Red Hat of the website or their entities, products or services. You agree that Red Hat is not responsible or liable for any loss or expenses that may result due to your use of (or reliance on) the external site or content.

Content from kubernetes.io is not included.Kubernetes version skew policies assert that all HA components must be no more than one minor version difference between all replicas, therefore OpenShift Container Platform (OCP) updates between minor versions must be serialized in HA clusters. In other words, you must update through every version, from OpenShift Container Platform 4.14 to 4.15 and then to 4.16. You cannot update from OpenShift Container Platform 4.14 to 4.16 directly. More information about preparing to perform an EUS-to-EUS update is available in the This page is not included, but the link has been rewritten to point to the nearest parent document.documentation.

Layered product and components update

Since OpenShift Container Platform 4.6, Red Hat-provided Operator catalog sources are distributed using index images, which contain pointers to a set of Operator manifests that Operator Lifecycle Manager (OLM) can query to discover and install. The index image is updated automatically whenever a cluster upgrade occurred so that Operator Lifecycle Manager can pull the most current version of Operators from the updated catalog sources.

During an EUS-to-EUS update, layered products/OLM Operators may require updates either before or during an EUS-to-EUS update to stay compatible with the OpenShift Container Platform.

Those updates are offered and made available in Operator update channels that exist between all OpenShift Container Platform versions involved. Changing the update channel of layered products/OLM Operators may be required to get the feasible version in order to continue the EUS-to-EUS update process.

Prerequisites

• Review the This page is not included, but the link has been rewritten to point to the nearest parent document.document for Preparing to perform an EUS-to-EUS update.

• Review the release notes and product lifecycles for any layered products and OLM Operators:

  • Some may require updates either before or during an EUS-to-EUS update.
  • Changing the update channel of layered products/OLM Operators may be required in between the EUS update to get the feasible version in order to continue the EUS-to-EUS update process (there is an example for ODF in how to upgrade ODF while doing OCP EUS-to-EUS upgrade).

• Check if any of the APIs removed in OpenShift 4.16 are in use by custom applications:

  • Navigating Kubernetes API deprecations and removals.
  • Preparing to upgrade to OpenShift Container Platform 4.15: (No Kubernetes API removals)
  • Preparing to upgrade to OpenShift Container Platform 4.16.

• Check the overall status of the cluster before starting the upgrade. If ODF is running on the cluster, check also the status of ODF:

  • OpenShift 4 cluster upgrade pre-checks requirements.
  • OpenShift Data Foundations (ODF) Operator Upgrade Pre-Checks.

• Review the following table outlines life-cycled layered products and components with support status throughout OpenShift 4.16 EUS.

  • Update channel and current version details for each layered product and component are available in the respective link in the following table.