Dell ObjectScale 1.3 Administration Guide

Upgrade Considerations for OpenShift Container Platform from 4.12 to 4.13

This section describes some aspects to consider while upgrading the OpenShift Container Platform (OCP) from 4.12 to 4.13.

OpenShift Container Platform cluster can be upgraded with a single operation on the OpenShift web console.

Before upgrading the platform, ensure you have upgraded ObjectScale to the latest <ObjectScale_Version>.

During Red Hat OpenShift upgrade, the Machine Config Operator (MCO) reboots primary and secondary nodes to apply the new configuration across a cluster. It cordons the number of nodes that is specified by the maxUnavailable field on the machine configuration pool and marks them as unavailable. By default, this value is set to "1". It then applies the new configuration and reboots each node.

As the nodes are updated by the Red Hat OpenShift Container Platform, the pods are restarted and returned to a schedulable state.

There is a risk that the rolling reboot driven by the MCO can bring ObjectScale offline by taking down too many nodes. This risk can be mitigated in the following ways:

• Ensure the MachineConfigPools are configured so that only one node is rebooted at a time, if the number of the nodes less than 10. The default maxUnavailable value is "1"
• Do not upgrade OCP from 4.12 to 4.13 in a four-node cluster.