Before you begin

Upgrade your ODF-RDR environment when a new version of Red Hat OpenShift on IBM Cloud, ACM, or ODF is available, or when any component is old or approaching deprecation. Failure to upgrade may result in future outages.

Wait until upgrade versions for all three components are available before you start. This reduces the overall upgrade effort.

Upgrading the hub cluster

Hub cluster

Upgrade both the control plane and worker nodes on the hub cluster before upgrading any add-ons.

1. Update the cluster master to the target version.

   ibmcloud oc cluster master update --cluster CLUSTER_NAME --version VERSION
   

2. Wait a few minutes, then confirm that the master update is complete.

   ibmcloud oc cluster ls
   

3. List the worker nodes and note the ID of each node to update.

   ibmcloud oc worker ls --cluster CLUSTER_NAME
   

4. Replace each worker node to update it to the same version as the master. Repeat for each worker node.

   ibmcloud oc worker replace --cluster CLUSTER_NAME --worker WORKER_NODE_ID --update
   

5. Confirm that all worker nodes are running the target version and show a Ready status.

   ibmcloud oc worker ls --cluster CLUSTER_NAME
   

Upgrading the managed clusters

Managed cluster

Because the managed clusters run ODF, follow the ODF-aware node upgrade procedure, which covers both the Red Hat OpenShift on IBM Cloud and ODF upgrades. For detailed instructions, see Updating or replacing VPC worker nodes that use ODF.

Upgrading ACM on the hub cluster

Hub cluster

After all clusters are running the target Red Hat OpenShift on IBM Cloud version, upgrade the ACM add-on on the hub cluster.

1. Upgrade the ACM add-on to the target version. Replace <cluster_id> with your hub cluster ID and <version> with the target ACM version (for example, 2.16).

   ibmcloud oc cluster addon update acm --cluster CLUSTER_ID --version VERSION
   

2. Confirm that the add-on updated successfully. In the output, verify the ACM add-on shows the target version.

   ibmcloud oc cluster addon ls --cluster CLUSTER_ID
   

Upgrading the ODF-DR operator on the hub cluster

Hub cluster

After ODF is upgraded on all managed clusters, upgrade the ODF Multicluster Orchestrator Operator on the hub cluster.

1. Confirm the current subscription channel for the ODF Multicluster Orchestrator operator.

   oc get subscription odf-multicluster-orchestrator -n openshift-operators -o jsonpath='{.spec.channel}'
   

2. Patch the subscription to the target channel. Replace stable-4.21 with the target version channel.

   oc patch subscription odf-multicluster-orchestrator -n openshift-operators \
     --type merge -p '{"spec":{"channel":"stable-4.21"}}'
   

3. Confirm that the install plan for the new version has been created and approved.

   oc get installplan -n openshift-operators
   

4. Verify that the CSV for the target version shows Succeeded status.

   oc get csv -n openshift-operators | grep odf-multicluster
   

5. Verify that the ODF Multicluster Orchestrator operator pods are running in the openshift-operators namespace.

   oc get pods -n openshift-operators | grep -i odf
   

   Confirm that both odf-multicluster-console and odfmo-controller-manager pods show Running status.

6. Verify that the DRPolicy is validated after reconciliation.

   oc get drpolicy -A
   

   Confirm that the VALIDATED column shows True for all policies. If not, run the following command to check the status conditions.

   oc describe drpolicy <drpolicy_name>
   

7. Verify that the MirrorPeer has finished reconciling.

   oc get mirrorpeers -A
   

   Confirm that the Phase shows ExchangedSecret. If it shows ExchangingSecret, verify Submariner connectivity before proceeding.

For more information, see Installing ODF Multicluster Orchestrator in the Red Hat documentation.

Upgrading optional operators

If your environment includes the following operators, upgrade them after the ODF-DR operator.

GitOps

For more information, see GitOps overview in the Red Hat documentation.

OADP

For more information, see Introduction to OpenShift API for data protection in the Red Hat documentation.

Next steps

After completing all upgrades, verify that the environment is healthy and that disaster recovery is functioning correctly. For detailed verification steps, see Verifying your ODF Regional Disaster Recovery configuration.