Upgrading with the CLI

Use these instructions to upgrade an existing IBM® Netcool® Operations Insight® Event Integrations Operator using the command line interface (CLI).

Upgrade the Catalog Source

1. Login to the cluster using the oc client.
2. In the target namespace, search for an existing CatalogSource resource for the IBM Netcool Operations Insight Event Integrations operator:

   kubectl get catalogsource --namespace $namespace
   

   If it is not in the target namespace, run the same command in the openshift-marketplace namespace.
3. Update the catalog source resource and upgrade image (spec.image) with the IBM Netcool Operations Insight Event Integrations catalog source image with image tag, for example:

   icr.io/cpopen/ibm-netcool-integrations-operator-catalog:<latest version>

   or with the image with digest, where <latest version> is the latest catalog source image tag. Click the Save button.

4. Give a few minutes for the operator catalog to update and verify that the operator pod is restarted and it is in Running state.

Upgrade the IBM Netcool Operations Insight Event Integrations operator

To upgrade to the latest operator version, the operator subscription must be updated to the latest subscription channel. You may skip this step if your operator is already subscribed to the latest update channel available and the Installation mode is specified as Automatic.

1. Get the existing Subscription resource.

   kubectl get subscription --namespace $namespace
   kubectl describe subscription <subscription name> --namespace $namespace

   Replace <subscription name> with the name of the existing Subscription resource.

2. Edit the Subscription resource from the previous step and change the spec.channel to the latest available subscription channel. The subscription channel follows the vX.Y format where X is the major version and Y is the minor version of the operator.
3. Describe the new InstallPlan resource for the new operator version:

   kubectl get installplan --namespace $namespace
   kubectl describe <install-plan resource>

   Replace <install-plan resource> with the name of the resource.

4. If the Approved field shows RequiresApproval or false, edit the InstallPlan resource and change the value of spec.approved to true.
5. Run the following command to get the .status.phase field of the InstallPlan resource and ensure that the value of changes to Complete:

   kubectl get installplan <install-plan resource> --namespace $namespace -o jsonpath='{.status.phase}'

Upgrade the Probe or Gateway instances

1. Run the command below to obtain the existing instance resources in the target namespace:

   kubectl get 
   prometheusprobe,pulsarprobe,jdbcgateway,pulsargateway,kafkaprobe,webhookprobe --namespace $namespace

2. Edit the probe or gateway instance and update its version specification (spec.version) using the kubectl edit <resource type> <resource name> command. It is recommended that you take a copy of the instance YAML before changing it, in case you later decide to rollback. For more information about configurable properties for each integration, see:
   • Deploying the Probe for Prometheus Integration
   • Deploying the Gateway for Kafka Integration
   • Deploying the JDBC Gateway Integration
   • Deploying the Gateway for Pulsar Integration
   • Deploying the Probe for Pulsar Integration
   • Deploying the Generic Webhook Probe
   • Deploying the Probe for Kafka Integration
3. Save the custom resource YAML.
4. Verify that the instance status shows OK that indicates the that upgrade was successful. Optionally, verify that all pods are running to ensure that the upgrade has completed successfully.