Upgrading with a new operator in the OpenShift console

You can upgrade your existing Content Cortex deployment by installing the new version of the operator into the project where the Content Cortex resides.

1. Log in to your cluster with an ID that has at least Operator permissions for the cluster.
   Note: If you want to use a global catalog that is shared across multiple deployments, you can select the openshift-marketplace namespace. Otherwise, you need to switch to your target namespace to create a private catalog for your deployment.
2. Add the CatalogSource resources to Operator Hub.
   To import the YAML into your cluster in the OCP Admin console:

   1. Click the plus icon at the top of the console. The Import YAML editor opens.

      

   2. Paste the CatalogSource resource definition into the editor, and click Create.
      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.

      apiVersion: operators.coreos.com/v1alpha1
      kind: CatalogSource
      metadata:
        name: ibm-content-operator-catalog
        namespace: openshift-marketplace
      spec:
        displayName: ibm-content-operator
        publisher: IBM
        sourceType: grpc
        image: icr.io/cpopen/ibm-fncm-catalog@sha256:<digest-xxxx>
        updateStrategy:
          registryPoll:
            interval: 45m

      Where, <digest-xxxx> is obtained from catalogsource.yaml from the case package.

   The CatalogSource resource adds the IBM Content Cortex Catalog to the OperatorHub, which depends on the catalog sources for IBM Content Cortex.

3. Find the IBM Content Cortex catalog item in the OperatorHub.
   In the OCP console, click Operators to open the OperatorHub, and then enter fncm in the Filter by keyword box under All items. Alternatively, you can find the IBM Content Cortex catalog item under Business Automation.
4. Click the IBM Content Cortex catalog item, and click Install.
   1. In the Create Operator Subscription wizard, select the channel and use the default for the approval strategy (Automatic).
      Note: When you create an operator subscription, by default Update approval (installPlanApproval) is set to "Automatic" to allow the IBM Content Cortex operator to automatically upgrade to newer versions when interim fixes are released.
   2. Select A specific namespace on the cluster under Installation Mode and select a namespace from the Installed Namespace drop-down list to install in a single or the operator's own namespace.

      Select the NAMESPACE that you created and prepared for the operator (fncm-project). The operator can be installed in multiple namespaces, but you must prepare each namespace beforehand. For more information, see Preparing a namespace for the operator.

      Important: The default mode is All namespaces on the cluster.

      Before you use the All namespaces on the cluster option, check the openshift-operators namespace to find installed operators. The openshift-operators namespace is watched by the Operator Lifecycle Manager (OLM).

   3. Click Install.
   4. In the Installed Operators view, verify the status of the Content Cortex installation.
5. Verify whether the operator is running.
   1. On the left panel in the OCP console, click Operators > Installed Operators.
   2. Make sure that the Content operator has the status "Succeeded" in your selected NAMESPACE:

      The OLM is now aware of the operators. A ClusterServiceVersion (CSV) for the operators appear in the target namespace, and APIs provided by the operators are available to use.

   Tip: If the Content Cortex operator is inactive for some time, you can delete the operator pod and let it reconcile.

oc logs -f deployment/ibm-content-operator -c operator

oc get role | grep ibm-content-operator | sort -t"t" -k1r | awk 'NR==1{print $1}'