Chapter 1. OpenShift Dedicated cluster upgrades You can schedule automatic or manual upgrade policies to update the version of your OpenShift Dedicated clusters. Upgrading OpenShift Dedicated clusters can be done through Red Hat OpenShift Cluster Manager or OpenShift Cluster Manager CLI. Red Hat Site Reliability Engineers (SREs) monitor upgrade progress and remedy any issues encountered. 1.1. Life cycle policies and planning To plan an upgrade, review the OpenShift Dedicated update life cycle guide in the "Additional resources" section. The life cycle page includes release definitions, support and upgrade requirements, installation policy information, and life cycle dates. You can use update channels to decide which Red Hat OpenShift Container Platform minor version to update your clusters to. OpenShift Dedicated supports updates only through the stable channel. To learn more about OpenShift update channels and releases, see Understanding update channels and releases . Additional resources For more information about the OpenShift Dedicated life cycle policy, see OpenShift Dedicated update life cycle . 1.2. Understanding OpenShift Dedicated cluster upgrades When upgrades are made available for your OpenShift Dedicated cluster, you can upgrade to the newest version through Red Hat OpenShift Cluster Manager or OpenShift Cluster Manager CLI. You can set your upgrade policies on existing clusters or during cluster creation, and upgrades can be scheduled to occur automatically or manually. Important Before upgrading a Workload Identity Federation (WIF)-enabled OpenShift Dedicated on Google Cloud Platform (GCP) cluster, you must update the wif-config. For more information, see "Cluster upgrades with Workload Identity Federation (WIF)". Red Hat Site Reliability Engineers (SRE) will provide a curated list of available versions for your OpenShift Dedicated clusters. For each cluster you will be able to review the full list of available releases, as well as the corresponding release notes. OpenShift Cluster Manager will enable installation of clusters at the latest supported versions, and upgrades can be canceled at any time. You can also set a grace period for how long PodDisruptionBudget protected workloads are respected during upgrades. After this grace period, any workloads protected by PodDisruptionBudget that have not been successfully drained from a node, will be forcibly deleted. Note All Kubernetes objects and PVs in each OpenShift Dedicated cluster are backed up as part of the OpenShift Dedicated service. Application and application data backups are not a part of the OpenShift Dedicated service. Ensure you have a backup policy in place for your applications and application data prior to scheduling upgrades. Note When following a scheduled upgrade policy, there might be a delay of an hour or more before the upgrade process begins, even if it is an immediate upgrade. Additionally, the duration of the upgrade might vary based on your workload configuration. 1.2.1. Recurring upgrades Upgrades can be scheduled to occur automatically on a day and time specified by the cluster owner or administrator. Upgrades occur on a weekly basis, unless an upgrade is unavailable for that week. If you select recurring updates for your cluster, you must provide an administrator's acknowledgment. OpenShift Cluster Manager does not start scheduled y-stream updates for minor versions without receiving an administrator's acknowledgment. Note Recurring upgrade policies are optional and if they are not set, the upgrade policies default to individual. 1.2.2. Individual upgrades If you opt for individual upgrades, you are responsible for updating your cluster. If you select an update version that requires approval, you must provide an administrator's acknowledgment. If your cluster version becomes outdated, it will transition to a limited support status. For more information on OpenShift life cycle policies, see OpenShift Dedicated update life cycle . 1.2.3. Upgrade notifications From OpenShift Cluster Manager console you can view your cluster's history from the Overview tab. The Upgrade states can be viewed in the service log under the Cluster history heading. Every change of state also triggers an email notification to the cluster owner and subscribed users. You will receive email notifications for the following events: An upgrade has been scheduled. An upgrade has started. An upgrade has completed. An upgrade has been canceled. Note For recurring upgrades, you will also receive email notifications before the upgrade occurs based on the following cadence: 2 week notice 1 week notice 1 day notice 1.2.4. Cluster upgrades with Workload Identity Federation (WIF) Before upgrading an OpenShift Dedicated on Google Cloud Platform (GCP) cluster with WIF authentication type to a newer y-stream version, you must update the WIF configuration to that version as well. Failure to do so before attempting to upgrade the cluster version will result in an error. For more information on how to update a WIF configuration, see the Additional resources section. Note The update path to a brand new release of OpenShift Dedicated is not available in the stable channel until 45 to 90 days after the initial GA of a newer y-stream version. Additional resources For more information about the service log and adding cluster notification contacts, see Accessing cluster notifications in Red Hat Hybrid Cloud Console . For more information on how to update a WIF configuration, see Updating a WIF configuration . 1.3. Scheduling recurring upgrades for your cluster You can use OpenShift Cluster Manager to schedule recurring, automatic upgrades for z-stream patch versions for your OpenShift Dedicated cluster. Based on upstream changes, there might be times when no updates are released. Therefore, no upgrade occurs for that week. Procedure From OpenShift Cluster Manager , select your cluster from the clusters list. Click the Upgrade settings tab to access the upgrade operator. To schedule recurring upgrades, select Recurring updates . Provide an administrator's acknowledgment and click Approve and continue . OpenShift Cluster Manager does not start scheduled y-stream updates for minor versions without receiving an administrator's acknowledgment. Important Before upgrading a Workload Identity Federation (WIF)-enabled OpenShift Dedicated on Google Cloud Platform (GCP) cluster, you must update the wif-config. For more information, see "Cluster upgrades with Workload Identity Federation (WIF)". Specify the day of the week and the time you want your cluster to upgrade. Click Save . Optional: Set a grace period for Node draining by selecting a designated amount of time from the drop down list. A 1 hour grace period is set by default. To edit an existing recurring upgrade policy, edit the preferred day or start time from the Upgrade Settings tab. Click Save . To cancel a recurring upgrade policy, switch the upgrade method to individual from the Upgrade Settings tab. Click Save . On the Upgrade settings tab, the Upgrade status box indicates that an upgrade is scheduled. The date and time of the scheduled update is listed. 1.4. Scheduling individual upgrades for your cluster You can use OpenShift Cluster Manager to manually upgrade your OpenShift Dedicated cluster one time. Procedure From OpenShift Cluster Manager , select your cluster from the clusters list. Click the Upgrade settings tab to access the upgrade operator. You can also update your cluster from the Overview tab by clicking Update to the cluster version under the Details heading. To schedule an individual upgrade, select Individual updates . Click Update in the Update Status box. Select the version you want to upgrade your cluster to. Recommended cluster upgrades appear in the UI. To learn more about each available upgrade version, click View release notes . If you select an update version that requires approval, provide an administrator's acknowledgment and click Approve and continue . Important Before upgrading a Workload Identity Federation (WIF)-enabled OpenShift Dedicated on Google Cloud Platform (GCP) cluster, you must update the wif-config. For more information, see "Cluster upgrades with Workload Identity Federation (WIF)". Click . To schedule your upgrade: Click Upgrade now to upgrade within the hour. Click Schedule a different time and specify the date and time that you want the cluster to upgrade. Click . Review the upgrade policy and click Confirm upgrade . A confirmation appears when the cluster upgrade has been scheduled. Click Close . Optional: Set a grace period for Node draining by selecting a designated amount of time from the drop down list. A 1 hour grace period is set by default. From the Overview tab, to the cluster version, the UI notates that the upgrade has been scheduled. Click View details to view the upgrade details. If you need to cancel the scheduled upgrade, you can click Cancel this upgrade from the View Details pop-up. The same upgrade details are available on the Upgrade settings tab under the Upgrade status box. If you need to cancel the scheduled upgrade, you can click Cancel this upgrade from the Upgrade status box. Warning In the event that a CVE or other critical issue to OpenShift Dedicated is found, all clusters are upgraded within 48 hours of the fix being released. You are notified when the fix is available and informed that the cluster will be automatically upgraded at your latest preferred start time before the 48 hour window closes. You can also upgrade manually at any time before the recurring upgrade starts.

Commands: