Online upgrade of IBM z/OS Connect

How to upgrade an online IBM z/OS Connect deployment.

Before you begin

The following role(s) are involved in this task.

Content applicable to Cloud
administrators

Restrictions: The upgrade cannot be removed or rolled back.
Remember: z/OS Connect API images are stateless and should be stored in your Container Registry. It is recommended to take a backup of the Red Hat® OpenShift® Container Platform cluster to preserve ConfigMaps, Secrets, and other configurations before upgrading. For more information, see Backup and restore.

Ensure cluster readiness: Ensure that your cluster still meets the deployment prerequisites. For more information, see Planning to install IBM z/OS Connect server.

Note: This procedure can be used on an online deployment of the IBM z/OS Connect Operator. If you have an offline deployment, follow the instructions in Offline upgrade of IBM z/OS Connect.

Procedure

Log in as cluster-admin to the Red Hat OpenShift Container Platform web console, and ensure that you are using the Administrator perspective by using the left navigation.
Configure automatic catalog polling.
Ensure that your catalog is set to automatically poll for the latest images. Your ibm-operator-catalog CatalogSource object can be configured to automatically poll for the latest catalog version and to retrieve it if one is available. Polling for updates is enabled by configuring the polling attribute, spec.updateStrategy.registryPoll. You might have already elected to automatically accept updates by adding the polling attribute to your ibm-operator-catalog YAML when you installed the IBM z/OS Connect Operator.

Use the following steps to check whether you already have a polling attribute set, and to configure it if you do not.
Attention: ibm-operator-catalog also contains the catalogs for other IBM Operators. If you have multiple IBM Operators that are installed on your cluster and you enable the polling attribute, then automatic update is configured for all of them.
1. Ensure that you are logged in as cluster-admin to the Red Hat OpenShift Container Platform web console by using the Administrator perspective.
2. Go to Administration > Cluster Settings.
3. Click Configuration, and then scroll down and click OperatorHub.
4. Select Sources, and then scroll down and click ibm-operator-catalog.
5. Click YAML to switch to the YAML view.
6. If there is not a spec.updateStrategy section, or spec.image is not set to icr.io/cpopen/ibm-operator-catalog:latest, then update the YAML to have the following in the spec block, and save it.
```
spec: 
  displayName: ibm-operator-catalog 
  publisher: IBM Content 
  sourceType: grpc 
  image: icr.io/cpopen/ibm-operator-catalog:latest 
  updateStrategy: 
    registryPoll: 
    interval: 45m
```
Verify the deployment.
Use the following procedure to check the status of your upgraded IBM z/OS Connect Operator deployment.
1. Ensure that you are logged in as cluster-admin to the Red Hat OpenShift Container Platform web console by using the Administrator perspective.
2. Click Operators > Installed Operators.
3. From the Project list, select the project (namespace) that IBM z/OS Connect Operator is deployed in.
4. Locate the IBM z/OS Connect Operator in the list, and verify that the annotation underneath it shows 1.0.7.