[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

Log into your cluster using cloudctl login (for IBM Cloud Pak® for Integration), or oc login.

Before you can upgrade the IBM MQ Operator in an airgap environment, you must mirror the latest IBM Cloud Pak for Integration images. See Preparing to upgrade the IBM MQ Operator or queue manager in an airgap environment.

Procedure

  1. Review Version support for the IBM MQ Operator to determine which operator channel to upgrade to.
  2. Optional: If you are upgrading from a version of IBM MQ Operator that is older than 1.5 to IBM MQ Operator 1.5 or later, you must first upgrade the version of IBM Cloud Pak foundational services.

    For more information, see Upgrading IBM Cloud Pak foundational services using the Red Hat OpenShift CLI.

  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/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

What to do next

If you upgraded to IBM Cloud Pak foundational services 3.7, any queue managers which use a IBM Cloud Pak for Integration license will need to be upgraded or restarted. For more information on how to do this, see Upgrading an IBM MQ queue manager using the Red Hat OpenShift CLI.