Installing the operators by using the Red Hat OpenShift console

Install the IBM Cloud Pak® for Integration operators by using the OpenShift web console.

You must be an OpenShift cluster administrator to install the operators. For more information, see OpenShift roles and permissions.

Operators extend a Kubernetes cluster by adding and managing more resource types in the Kubernetes API and enabling the installation and management of software by using standard Kubernetes tools. For more information, see Operator reference.

Before you begin

Decide which installation mode to use to install the operators; you will specify this mode during the procedure. For more information, see Installing the operators.

Attention: The IBM Cloud Pak foundational services operator is no longer installed automatically. Install this operator manually if you need to create an instance that uses identity and access management. Install this operator in the same installation mode as the IBM Cloud Pak for Integration operator. If you have your own instance of Keycloak installed in your cluster, install the Cloud Pak foundational services operator in a different namespace. Cloud Pak for Integration uses only the Keycloak installation that is installed by Cloud Pak foundational services.
Important: The API Connect cluster, Event Manager, and Event Processing instances require you to install an appropriate certificate manager. Follow the instructions in Installing the cert-manager Operator for Red Hat OpenShift to fulfill this requirement.

Procedure

Install operators that provide the instances you want to use. For example, if you install the IBM API Connect operator now, you can deploy API Connect cluster instances later. For more information, see Operators available to install.

  1. Log in to the OpenShift web console with your OpenShift cluster administrator credentials.

  2. Make sure that the Administrator perspective is selected.

  3. Click Operators > OperatorHub.

    Select the Administrator perspective, then click Operators > OperatorHub
  4. On the OperatorHub page that opens, use the search filter to locate the tile for the operator you plan to install, for example, IBM Cloud Pak for Integration, and click the tile:

    Click the tile for the operator that you want
  5. On the operator information page that opens, click Install.

    Click Install
  6. In the Install Operator page that opens:

    • From the Update channel list, select the operator channel. The Instana agent doesn't have an operator channel, so if you are installing the Instana agent, skip this substep. For more information about available operators and operator channel versions, see Operator and instance versions for this release.

    • Select the installation mode: either All namespaces on the cluster or A specific namespace on the cluster, according to the decision that you made in the "Before you begin" section of this task.

      Select an installation mode of All namespaces on the cluster or A specific namespace on the cluster
    • If you select the option to install the operator in A specific namespace on the cluster, create a new project for this purpose. Under Home > Projects, click Create Project, enter the name for your new project, and click Create.

    • For the approval strategy, do not select Manual, because it doesn't allow users to control which updates to apply, and it can block upgrades. The default strategy is Automatic.

      Selecting the approval strategy: automatic is the default
  7. Click Install. The operator installs.

  8. Confirm installation. To confirm the operator is installed:

    1. Make sure that you're logged in to the OpenShift web console.

    2. In the navigation panel, click Operators > Installed Operators.

    3. From the Project list, select the namespace in which the operator was installed. If you installed the operator by using the All namespaces on the cluster installation mode, the operator pod is located in the openshift-operators project.

    4. Locate your operator in the table and examine the status column. When the operator is ready, the status changes to Succeeded.

      Confirm that the operator is installed

You can now install other Cloud Pak for Integration operators.

Operators available to install

The following table lists each operator that you can install and the instance types that it supports. You can install any combination of operators, and any dependencies are pulled in automatically.

Important: Not all operators are supported on every environment. For more information, see "Supported environments for operators" in Operating environment

Installing the IBM Cloud Pak for Integration operator enables deployment of the Platform UI, which facilitates the deployment and management of the other instances.

Operator name Instances
IBM Cloud Pak for Integration Platform UI, Assembly, API, API Product, Messaging server, Messaging channel, Messaging queue, Messaging user
IBM Automation foundation assets Automation assets
IBM API Connect API Connect cluster, API Manager, API Analytics, API Portal, API Gateway
IBM App Connect Integration dashboard, Integration design, Integration runtime
IBM Aspera HSTS High speed transfer server
IBM DataPower Gateway Enterprise gateway
IBM Event Streams Kafka cluster, Kafka topic, Kafka user, Kafka Connect runtime, Kafka connector
IBM Event Endpoint Management Event Manager, Event Gateway
IBM Event Processing Event Processing
IBM Operator for Apache Flink Flink
IBM MQ Queue manager
IBM Instana Agent IBM Instana
IBM Cloud Pak foundational services* Cloud Pak foundational services for Cloud Native PostgreSQL and RedHat Build of Keycloak only
cert-manager Operator for Red Hat OpenShift Certificate management
IBM Licensing IBM License Service and IBM License Service reporter. For more information, see Deploying License Service.

* When installing the Cloud Pak foundational services operator, if there is more than one tile for "IBM Cloud Pak foundational services", click the tile with the catalog source of ibm-cp-common-services. Do not click the tile with the catalog source of Certified or ibm-cs-install.

For more information about available instances, see Deploying instances.