[OpenShift Container Platform][IBM Cloud Pak for Integration]

Upgrading the IBM MQ Operator using the Red Hat OpenShift CLI

The IBM® MQ Operator can be upgraded from the command line.

Before you begin

Note: The latest CD version of the IBM MQ Operator is 3.1.3. The latest LTS version of the IBM MQ Operator is 2.0.29. For the latest IBM MQ Operator release notes, see Release history for IBM MQ Operator.

Log into your cluster using oc login.

Before you can upgrade the IBM MQ Operator in an air-gap environment, you must mirror the latest IBM Cloud Pak® for Integration images. For upgrading to IBM MQ Operator 3.0 or above, Migrating to the current CD channel of the IBM MQ Operator includes the air-gap specific steps. For upgrading to earlier IBM MQ operator versions, See [Deprecated]Preparing to upgrade to the latest IBM MQ 2.x Operator or queue manager in an air-gap environment.

Procedure

  1. Review Version support for the IBM MQ Operator to determine which operator channel to upgrade to.
  2. Apply latest Catalog source.

    If you are using the IBM MQ specific catalog source (all air-gap installs), rather than the ibm-operator-catalog, you must apply the catalog source for your IBM MQ version.

    Follow the instructions in Adding catalog sources to a cluster.

    Note: If you have already completed the operator install step for air-gap Mirror images (air-gap only), you only have to complete the step that applies the catalog source. For example:
    oc apply -f ~/.ibm-pak/data/mirror/${OPERATOR_PACKAGE_NAME}/${OPERATOR_VERSION}/catalog-sources.yaml
  3. Upgrade the IBM MQ Operator. New major/minor IBM MQ Operator versions are delivered through new Subscription Channels. To upgrade your Operator to a new major or minor version, you will need to update the selected channel in your IBM MQ Operator Subscription.
    1. Ensure the required IBM MQ Operator Upgrade Channel is available.
      oc get packagemanifest ibm-mq -o=jsonpath='{.status.channels[*].name}'
    2. Patch the Subscription to move to the desired update channel (where vX.Y is the desired update channel identified in the previous step.
      oc patch subscription ibm-mq --patch '{"spec":{"channel":"vX.Y"}}' --type=merge