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.

Before running any commands in this step, set your CLI context to the hub cluster.

ibmcloud oc cluster config --cluster HUB_CLUSTER_NAME --admin

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. This may take several minutes.

   ibmcloud oc worker ls --cluster CLUSTER_NAME
   

Upgrading the managed clusters

Managed cluster

Before running any commands in this step, set your CLI context to the managed cluster you are upgrading. Repeat for each managed cluster.

ibmcloud oc cluster config --cluster MANAGED_CLUSTER_NAME --admin

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.

Before running any commands in this step, set your CLI context to the hub cluster.

ibmcloud oc cluster config --cluster HUB_CLUSTER_NAME --admin

1. Upgrade the ACM add-on to the target version. Replace CLUSTER_NAME with the name of your hub cluster and VERSION with the target ACM version (for example, 2.16).

   ibmcloud oc cluster addon update acm --cluster CLUSTER_NAME --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_NAME
   

Upgrading the ODF Multicluster Orchestrator on the hub cluster

Hub cluster

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

The OpenShift DR Hub Operator and OpenShift DR Cluster Operators are installed as dependencies of the ODF Multicluster Orchestrator and are upgraded automatically. You do not need to upgrade them manually.

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

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

2. Patch the subscription channel to the version that matches the ODF version you upgraded to on your managed clusters. The channel follows the format stable-X.Y, where X.Y is the ODF version. For example, if you upgraded ODF to 4.21, use stable-4.21.

   The ODF Multicluster Orchestrator version must match the ODF version installed on your managed clusters. Using a mismatched version may cause the DR policy to fail validation.

   To confirm which channels are available, run the following command.

   oc get packagemanifest odf-multicluster-orchestrator -n openshift-marketplace -o jsonpath='{.status.channels[*].name}'
   

   Then patch the subscription to the target channel. Replace stable-4.21 with the channel that matches your ODF version.

   oc patch subscription.operators.coreos.com 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.

   oc get installplan -n openshift-operators
   

   If the install plan for the target version shows APPROVED: false, you must manually approve it before the upgrade proceeds. Replace INSTALLPLAN_NAME with the name of the install plan for the target version.

   oc patch installplan INSTALLPLAN_NAME -n openshift-operators --type merge -p '{"spec":{"approved":true}}'
   

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.