Upgrading with an existing operator in the OpenShift console

You can upgrade an existing Content Cortex deployment by upgrading the existing operator to a new version in the OpenShift® console.

Procedure

  1. Log in to your OCP cluster as a cluster administrator.
  2. Add the CatalogSource resources to the OpenShift Operator Hub for the new versions. Each interim fix has a specific version and unique digest, which are needed for the new catalog sources.
    1. Select Home → Search, and switch your project to openshift-marketplace.
      Note: If you want to use a global catalog that is shared across multiple deployments, you can select the openshift-marketplace project. Otherwise, you need to switch to your target project to create a private catalog for your deployment.
    2. Search for CatalogSource, and select ibm-content-operator-catalog.
    3. Select the YAML tab and copy the image from the catalogsource.yaml file to the console.
    4. Click Save.
    Note: You can find the CatalogSource YAML in the catalog_source.yaml file, which is located in the ibm-content-cortex-containers repository in the /descriptors/op-olm directory.

    For more information about downloading ibm-content-cortex-containers, see Preparing a client to connect to the cluster.

    To apply the new catalog versions, go to a command line and run the following command: 
    oc apply -f catalog_source.yaml
  3. In the Subscription tab of the Content Cortex operator, click to edit the Channel, select the v26.0 channel, and click Save.
    The Content Cortex operator is automatically updated to version 26.0.0.
  4. Click Installed Operators to see the updated operator.
    If the Content Cortex operator upgrade continues to show the status "Upgrading", then you might need to intervene.

    To resolve the issue remove the previous versions of the operator by clicking the three vertical dots (overflow menu) in the far right column, click Uninstall Operator, and then install the operator again from the Openshift cluster OperatorHub.

What to do next

When started, you can monitor the operator logs with the following command.
oc logs -f deployment/ibm-content-operator
When the operator is deployed successfully, get the role of the operator to give access to specified users.
oc get role | grep ibm-content-operator | sort -t"t" -k1r | awk 'NR==1{print $1}'
Once the operator is upgraded, and an updated custom resource is applied, the deployment upgrade starts. This can take approximately 20 minutes, and after one reconcile loop completes, you can validate your upgrade. To validate the success of your upgrade, see topic Verifying the upgrade.