Installing the operators by using the Red Hat OpenShift console

Review Operator reference before you install the operators.

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.

   

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:

   

5. On the operator information page that opens, click Install.

   

6. In the Install Operator page that opens:

   • 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 option to install either in all namespaces in the cluster or in a specific namespace. The Instana agent can be installed only in all namespaces. For more information, see Guidelines for installing operators.

     

   • If you select the option to install the operator in a specific namespace, 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 upgrade. The default strategy is Automatic. For more information, see Restricting automatic updates with an approval strategy.

     

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.

      

You can now install other Cloud Pak for Integration operators.

Controlling updates by using dedicated and declarative catalog sources is the only way to ensure that the cluster never upgrades. To use this method, follow the procedure in the "Adding specific catalog sources for each operator" section of Adding catalog sources to a cluster.

However, if you know you will always want automatic upgrades of operators, and you do not require declarative installs, you can use the IBM Operator catalog for installations.

There are two approval strategies, Automatic and Manual.

• Do not use the Manual strategy, because users cannot control what upgrades to apply; this strategy forces all possible upgrades to be done at the same time. It can also block an upgrade. If your use case requires that you control what upgrades to apply, follow the procedure for "Adding specific catalog sources for each operator" as already described.

• The Automatic strategy is the default strategy. As new operator versions are made available on the subscription channel (only if the catalog source is updated), they are installed automatically, but only on fix packs. Minor version changes always require user input to change subscription channels.

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.

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

Follow one of these topics, depending on how you are installing Cloud Pak for Integration:

• For online environments, see Finding and applying your entitlement key by using the UI (online installation).

• For air-gapped environments, see Deploying the Platform UI.