Installing operators using the OpenShift console

You can use the OpenShift® console to install operators for a new IBM Content Cortex container deployment, or to add the IBM Content Cortex AI Services operator to an existing traditional deployment.

1. From the OpenShift console, log in to your cluster with an ID that has at least Operator permissions for the cluster.
2. Add the CatalogSource resources to OperatorHub.
   1. In the OpenShift console, click the plus icon to open the Import YAML editor.
      
   2. Paste the CatalogSource resource definition into the editor.
      Note: You can find the CatalogSource YAML in the catalog_source.yaml file in the GitHub repository under ibm-content-cortex-containers/descriptors/op-olm. For more information about downloading ibm-content-cortex-containers, see Preparing a client to connect to the cluster.

      Replace XXXXXXXXXXXX with the digest for each catalog source. Replace the <namespace> placeholder with openshift-marketplace for the global catalog namespace or your target Content Cortex namespace, for example, ccx-project, for a private catalog.

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

      Get <digest-xxxx> from catalog_source.yaml in the case package.

   3. Click Create.
      The IBM Content Cortex Catalog is added to OperatorHub.
3. Find the required operator catalog items in OperatorHub.
   In the OpenShift console, click Operators to open OperatorHub, and then enter IBM in the Filter by keyword box under All items. Alternatively, you can find the operators under Business Automation.
4. Install the IBM Content operator.
   If CPE is already deployed and you want to add only AI Services, skip this step. Otherwise, click the IBM Content catalog item, and click Install.
   1. In the Create Operator Subscription wizard, select the channel (v 26.0 for 26.0.0) 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 Content 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 list to install in a single or the operator's own namespace.

      Select the namespace that you created and prepared for the operator, for example, ccx-project. If you install the operator in multiple namespaces, 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 this option, check the openshift-operators namespace for existing operators because Operator Lifecycle Manager (OLM) watches that namespace.
   3. Click Install.
   4. In the Installed Operators view, verify the status of the Content Cortex installation.
5. Install the IBM License Service operator.
   If your deployment already includes IBM License Service, skip this step. Otherwise, click the IBM License Service catalog item, and click Install.
   1. In the Create Operator Subscription wizard, select the appropriate channel and use the default approval strategy (Automatic).
   2. Select A specific namespace on the cluster under Installation Mode and select ibm-licensing from the Installed Namespace list.
      Important: The IBM License Service operator must be installed in the ibm-licensing namespace.
   3. Click Install.
   4. In the Installed Operators view, verify the status of the IBM License Service operator installation.
6. Install the IBM Usage Metering operator.
   Click the IBM Usage Metering catalog item, and click Install.
   1. In the Create Operator Subscription wizard, select the appropriate channel and use the default approval strategy (Automatic).
   2. Select A specific namespace on the cluster under Installation Mode and select the same namespace as the Content operator (for example, ccx-project) from the Installed Namespace list.
   3. Click Install.
   4. In the Installed Operators view, verify the status of the IBM Usage Metering operator installation.
7. Install the IBM Content Cortex AI Services operator.
   If you have an existing traditional Content Platform Engine deployment, this is the only operator that you install. If you want AI capabilities for a new IBM Content Cortex container deployment, complete this step. Click the IBM Content Cortex AI Services catalog item, and click Install.
   1. In the Create Operator Subscription wizard, select the appropriate channel and use the default approval strategy (Automatic).
   2. Select A specific namespace on the cluster under Installation Mode and select the same namespace as the Content operator (for example, ccx-project) from the Installed Namespace list.
   3. Click Install.
   4. In the Installed Operators view, verify the status of the IBM IBM Content Cortex AI Services operator installation.
8. Verify that all operators are running.
   1. In the OpenShift console, click Operators > Installed Operators.
   2. In the namespace where you installed the Content operator, for example, ccx-project, verify that the following operators have the status Succeeded:
      • Content operator
      • IBM Usage Metering operator
      • IBM Content Cortex AI Services operator, if installed
   3. In the ibm-licensing namespace, verify that the IBM License Service operator has the status Succeeded.
   4. Verify the operator installations.

      

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

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