Deploying Cloud Pak for Integration using the OpenShift console

1. Log into the OpenShift web console with your OpenShift cluster admin credentials.

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

3. Change Project to the desired project/namespace name. Click the drop-down arrow and select your project name from the list.

4. In the list on the Installed Operators panel, find and click IBM Cloud Pak for Integration.

5. Click the Platform UI tab.

6. Click Create PlatformNavigator. The Create PlatformNavigator panel opens, and offers two methods for configuring the resource; the Form view and the YAML view. The Form view is selected by default:

   

Configuring in the Form view

1. Change Project to your project (namespace) name. Click the drop-down arrow and select your project name from the list.

2. In the Name field, enter a name for the new instance or leave the default.

3. Next to License, click the arrow to expand the license acceptance section.

4. Set License Accept to true if you accept the Cloud Pak for Integration license agreement. For details, see Licensing.

   

5. For License LI, click the arrow to open the drop-down list, and select a license. For details about specific licenses, see the "Table of license versions" section in Licensing

6. Specify the Storage class. Click the arrow to expand the Storage pane, then click the arrow for Select Storage Class and select a file storage class a file storage class that supports ReadWriteMany (RWX) volumes and allows read and write access to non-root users. Supported storage providers include ibmc-file-gold-gid, OpenShift Data Foundation (formerly OpenShift Container Storage), Spectrum, and Portworx. For additional details about storage support and configuration, see Storage considerations.

   
   Note: If you don't see any options in the Storage Class list, you need to create one or more storage options. See the Requirements section for more information.

7. Set any other configuration values as appropriate.

8. Click Create.

Your instance of the Cloud Pak is added to the list of instances in the current project (namespace).

Configuring in the YAML view

The YAML view opens an editor containing an example YAML file for a resource. Update the values in the file per the following steps.

1. Change metadata.namespace to your project (namespace) name.

2. Change spec.license.accept to true if you accept the Cloud Pak for Integration license agreement. For details, see Licensing.

3. Change the value of spec.license.license to the license string that matches your version of Cloud Pak for Integration. See the section, Table of license versions in Licensing for more information.

4. For spec.storage.class, specify a file storage class a file storage class that supports ReadWriteMany (RWX) volumes and allows read and write access to non-root users. Supported storage providers include ibmc-file-gold-gid, OpenShift Data Foundation (formerly OpenShift Container Storage), Spectrum, and Portworx. For additional details about storage support and configuration, see Storage considerations.

5. Click Create.

Your instance of Cloud Pak for Integration is added to the list of instances in the current project (namespace).

When the Platform UI status changes to Ready, log in to the Platform UI for the first time to create users and permissions.

1. In the navigation panel of the OpenShift web console, click Operators > Installed Operators.

2. Click to expand the Project list and select the project where the Platform UI is deployed.

3. In the Installed Operators pane, click IBM Cloud Pak for Integration.

4. Click Platform UI.

5. In the PlatformNavigators list, click the name of the deployed instance.

6. In the Metadata section, click the link under Cloud Pak UI.

   

7. At the login screen, click OpenShift authentication and log in with your OpenShift cluster admin credentials.

   

   If you are unable to log in with your OpenShift credentials, click IBM provided credentials (admin only) and:

   • For Username, enter admin.

   • For Password, enter the IBM admin password you obtain in the next section.

8. The Platform UI opens. You can now create users and permissions by clicking Manage users. For detailed information, see Adding users in the IBM Cloud Pak Platform UI and the other topics in the Identity and access management section.

   Note: If you followed the steps in Getting the initial admin password, you need to create an OpenShift admin user and change the admin user password.

9. After you have completed your tasks in the Platform UI, you can perform additional post-installation tasks such as configuring the foundational services and enabling monitoring. For additional information, see System administration.

If you are unable to log in to Platform UI with OpenShift cluster admin credentials (for example, if you are installing in a cluster using Red Hat OpenShift Service on AWS (ROSA), follow these steps:

1. Log in to the OpenShift web console with your OpenShift cluster admin credentials. Make sure the Administrator perspective is selected.

   

2. In the navigation panel, click to expand Workloads, then select Secrets.

3. Switch to the ibm-common-services project:

   • At the top of the Secrets pane, click the arrow to expand the Project list, and select ibm-common-services.

   • Enter platform-auth-idp-credentials in the search box (optional) and click platform-auth-idp-credentials in the list.

4. Scroll down to the Data pane and copy the value for admin_password.

   

   Save the password to use when logging in to Platform UI.

To log out of Cloud Pak for Integration click the user menu icon in the top banner, and then click Log out:

The following table lists the configurable parameters and default values for the custom resource.

spec.nodeSelector:

Shows how to use the nodeSelector section in the Platform UI spec to configure the nodes where the deployment will run.

spec:
  nodeSelector:
    key1: value1
    key2: value2

spec.labels:

Shows how to use the labels section in the Platform UI spec to apply labels to the deployment.

spec:
  labels:
    key1: value1
    key2: value2

spec.annotations:

Shows how to use the annotations section in the Platform UI spec to apply annotations to the deployment.

spec:
  annotations:
    key1: value1
    key2: value2

spec.resources:

Shows how to use the resources section in the Platform UI spec to allocate resource requests and limits.

spec:
  resources:
    navigator:
      limits:
        cpu: '1'
        memory: 512Mi
      requests:
        cpu: '0.25'
        memory: 256Mi
    services:
      limits:
        cpu: '1'
        memory: 512Mi
      requests:
          cpu: '0.25'
          memory: 256Mi

spec.template:

Shows how to use the template section in the Platform UI spec to customize the containers.

spec:
  template:
    pod:
      containers:
        - image: placeholder
          imagePullPolicy: IfNotPresent
          name: ibm-cp4i-prod-navigator
        - image: placeholder
          imagePullPolicy: IfNotPresent
          name: ibm-cp4i-prod-services
      imagePullSecrets:
        - ibm-entitlement-key
        - other-key

spec.requestIbmServices:

Shows how to use the requestIbmServices section in the Platform UI spec to control the IBM Cloud Pak foundational services requested.

spec:
  requestIbmServices:
    monitoring: true/false
    metering: true/false
    licensing: true/false

spec.loggingUrl:

Shows how to use the loggingUrl section in the Platform UI spec to enable usage of a custom logging stack.

spec:
  loggingUrl: "https://host.apps.cluster.domain.com/kibana"

For information on cluster-scoped permissions for the Cloud Pak for Integration operator, see Required cluster-scoped permissions for the IBM Cloud Pak for Integration instance.