Installing the IBM Events Operator for watsonx Assistant or watsonx Orchestrate

If you plan to install watsonx Assistant or watsonx Orchestrate in this instance of IBM Software Hub, you must install the IBM Events Operator for the instance.

Installation phase
  • You are not here. Setting up a client workstation
  • You are not here. Setting up a cluster
  • You are not here. Collecting required information
  • You are not here. Preparing to run installs in a restricted network
  • You are not here. Preparing to run installs from a private container registry
  • You are not here. Preparing the cluster for IBM Software Hub
  • You are here icon. Preparing to install an instance of IBM Software Hub
  • You are not here. Installing an instance of IBM Software Hub
  • You are not here. Setting up the control plane
  • You are not here. Installing solutions and services
Who needs to complete this task?

Cluster administrator A cluster administrator must complete this task.

When do you need to complete this task?
Complete this task only if you plan to install one of the following services in this instance of IBM Software Hub:
  • watsonx Assistant
  • watsonx Orchestrate
    • Required only if you plan to use agentic_assistant mode.
    • Not required if you plan to use agentic mode.

Repeat as needed If you plan to install multiple instances of IBM Software Hub on the cluster, repeat this task for each instance where you plan to install either of the preceding services.

Before you begin

You must complete Installing Red Hat OpenShift Serverless Knative Eventing before you can install the IBM Events Operator for the instance.

Best practice: You can run many of the commands in this task exactly as written if you set up environment variables for your installation. For instructions, see Setting up installation environment variables.

Ensure that you source the environment variables before you run the commands in this task.

About this task

watsonx Assistant and watsonx Orchestrate use the IBM Events Operator to log events and right to be forgotten (RTBF) requests.

Use the deploy-events-operator command to install the IBM Events Operator for this instance of IBM Software Hub.

Procedure

  1. Log the cpd-cli in to the Red Hat OpenShift Container Platform cluster: 
    ${CPDM_OC_LOGIN}
    Remember: CPDM_OC_LOGIN is an alias for the cpd-cli manage login-to-ocp command.
  2. Install the IBM Events Operator:
    The cluster pulls images from the IBM Entitled Registry 
    cpd-cli manage deploy-events-operator \
--release=${VERSION} \
--events_operator_ns=${PROJECT_CPD_INST_OPERATORS} \
--events_operand_ns=${PROJECT_CPD_INST_OPERANDS} \
--image_pull_secret=${IMAGE_PULL_SECRET}
    The cluster pulls images from a private container registry 
    cpd-cli manage deploy-events-operator \
--release=${VERSION} \
--events_operator_ns=${PROJECT_CPD_INST_OPERATORS} \
--events_operand_ns=${PROJECT_CPD_INST_OPERANDS} \
--docker_registry=${PRIVATE_REGISTRY_LOCATION} \
--image_pull_secret=${IMAGE_PULL_SECRET}

What to do next

Now that you've installed the IBM Events Operator, you're ready to complete Annotating IBM Software Hub projects (namespaces) to enable embedded Db2 databases to use the restricted-v2 SCC.