Non-disruptive migration of the z/OS Cloud Broker Operator and installed suboperators

You can perform a full migration to the latest version of z/OS Cloud Broker without disrupting existing suboperator workloads.

Important: Do not delete the existing suboperator instances before performing the migration to avoid disruption to existing suboperator workloads. This ensures that the existing workloads remain online throughout the migration process.

Prerequisites

Ensure that you can access the Red Hat OpenShift Container Platform cluster web console using an account with cluster-admin permissions.

Procedure

  1. Log in to the Red Hat OpenShift Container Platform web console for your cluster by using your cluster-admin credentials. (See Logging in to Red Hat OpenShift Container Platform.)

  2. Without deleting the existing ZosEndpoints, delete all OperatorCollections and SubOperatorConfigs by completing the following steps:

    1. In the Red Hat OpenShift Container Platform navigation pane, select Operators > Installed Operators.

      Installed Operators selection

    2. From the Projects drop-down list, select the project from which you are performing the migration.

    3. In the Name column on the Installed Operators page, select IBM z/OS Cloud Broker.

      z/OS Cloud Broker Operator selection on Installed Operators page

    4. On the "Operator details" page, select the Operator Collection tab.

      "Operator Collection" tab selection on the "Operator details" page

    5. For each OperatorCollection, select the three dots at the end of the row and then select Delete OperatorCollection.

      Operator Collection tab, Delete selection

    6. On the "Delete OperatorCollection?" dialog box, select Delete.

      Delete button on the "Delete OperatorCollection?" dialog box

    7. Repeat steps e–f until all OperatorCollections are removed.

    Step results: All OperatorCollections are removed from the Operator Collection tab on the "Operator details" page.

    Operator Collection tab on the "Operator details" page, all OperatorCollections removed

    All SubOperatorConfigs are removed from the SubOperator Config tab on the "Operator details" page.

    SubOperator Config tab on the "Operator details" page, all SubOperatorConfigs removed

  3. Without deleting the existing z/OS Cloud Broker instance, uninstall the z/OS Cloud Broker operator by completing the following steps:

    1. Return to the "Installed Operators" page.

    2. Ensure that the project from which you are performing the migration is still selected in the Projects drop-down list.

    3. In the z/OS Cloud Broker Operator row, select the three dots at the end of the row and then select Uninstall Operator.

      Delete z/OS Cloud Broker Operator selection on the Installed Operators page

    4. On the "Uninstall Operator?" dialog box, select Uninstall without checking the Delete all operand instances for this operator checkbox.
      Uninstall button on the "Uninstall Operator?" dialog box

    Step result: The z/OS Cloud Broker Operator is removed from the "Installed Operators" page.

  4. Reinstall the latest version of z/OS Cloud Broker Operator. (See Installing the z/OS Cloud Broker Operator.)

  5. Reimport and reconfigure the operator collections. (See Importing an operator collection.)

Procedure results

After the latest version of z/OS Cloud Broker Operator is installed and the operator collections are imported and configured, the existing z/OS Cloud Broker instance will reconcile and install the latest images for each component.