OSD 4.11 clusters require user action before scheduling a minor version upgrade

Solution Unverified - Updated

Environment

  • Red Hat OpenShift Dedicated (OSD)
    • 4.11

Issue

  • OpenShift Dedicated clusters upgrading from 4.11 to 4.12 need cluster owner action to ensure stability of the cluster through and after the upgrade operation.
  • To ensure that OpenShift Dedicated cluster owners understand the changes occurring as as part of upgrading the underlying Kubernetes to v1.25, there are acknowledgements necessary to ensure cluster owners have taken necessary precautions.

Resolution

Note: For ROSA 4.11 upgrades, please refer to: ROSA 4.11 clusters require user action before scheduling a minor version upgrade.

Prerequisites

Before starting with the upgrade to OpenShift 4.12 (which uses Kubernetes 1.25), as a significant number of deprecated APIs are removed in that version, it's necessary to review KCS 6955381: Preparing to upgrade to OpenShift Container Platform 4.12 to understand the changes and to verify if those changes could affect the custom applications in the cluster.

Upgrade

To upgrade from from 4.11 to 4.12, the following tasks need to be done:

  1. Select your cluster from the cluster list at This content is not included.This content is not included.https://console.redhat.com/openshift
    You should land at your cluster's overview
  2. Go to the Settings tab
  3. Click the 'Update' button in the 'Update Status' box.
  4. Proceed through the steps to acknowledge you have prepared for the deprecated APIs and then schedule your upgrade.

Note: If you rely on the recurring/automatic update strategy, you will only need to acknowledge preparedness for the deprecated APIs, before allowing your upgrade to occur.

Root Cause

OpenShift Dedicated clusters upgrading from 4.11 to 4.12 need cluster owner action to ensure stability of the cluster through and after the upgrade operation.

For additional information about Kubernetes deprecated APIs, refer to:

Diagnostic Steps

Check if the cluster is in version 4.11:

$ oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.xx    True        False         8d      Cluster version is 4.11.xx

It's also possible to check the version of the cluster in the This content is not included.OCM console.

SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.