Deploying the Platform UI by using the OpenShift console
Deploying the IBM Cloud Pak Platform UI allows you to deploy and manage instances from a central location. This task must be performed by a cluster administrator. For more information, see Roles and permissions.
This procedure describes how to deploy and configure the IBM Cloud Pak Platform UI using the OpenShift web console. To deploy using the CLI, see Deploying the Platform UI by using the CLI.
Prerequisites
You are on a supported version of Red Hat OpenShift Container Platform. For more information, see Operating environment.
If you have an online cluster and have not already created a secret called
ibm-entitlement-key
in the namespace where the instance will be created, see Finding and applying your entitlement key by using the UI (online installation).- An OpenShift cluster administrator has created one or more storage classes that support
ReadWriteMany
(RWX) and allows read and write access to non-root users. Supported storage providers includeibmc-file-gold-gid
, OpenShift Data Foundation (formerly OpenShift Container Storage), Spectrum, and Portworx. For additional details about storage support and configuration, see Storage considerations.Tip: For OpenShift Data Foundation in a production environment, the optimal minimum deployment is 4 storage nodes, with 3 Object Storage Daemons (OSDs) on each node. This provides much greater data resiliency in the event of any OSD failures.
To deploy the Platform UI with an RWO storage class, follow the procedures in Deploying the Platform UI with RWO storage.
Deploying with OpenShift web console guided documentation
Log into the OpenShift web console with your OpenShift cluster admin credentials.
In the navigation pane, click Home > Overview.
In the Build with guided documentation section, click View all quick starts.
In the Quick Starts panel, click the tile for Getting started with the Cloud Pak for Integration.
- In the panel that opens, follow the procedures to deploy the Platform UI.Tip: If you have followed all the procedures up to this point, you can skip the Prerequisites section.
Deploying with the OpenShift web console
Complete these tasks to create and get access to your instance of the Platform UI:
Creating the Platform UI instance
Log into the OpenShift web console with your OpenShift cluster admin credentials.
If you installed the operators in All namespaces on the cluster mode, use a project other than
openshift-operators
in which to deploy the instance.If needed, create a new project for this purpose. Under Home > Projects, click Create Project, enter the name for your new project, and click Create.
In the navigation panel, click Operators > Installed Operators.
In the list on the Installed Operators panel, find and click IBM Cloud Pak for Integration.
Click the Platform UI tab.
Click Create PlatformNavigator. The Create PlatformNavigator panel opens.
Change Project to your project (namespace) name. Click the drop-down arrow and select your project name from the list.
Create the Platform UI with either the "Form view" or the "YAML view".
Configuring in the Form view
The Form view opens a form that lets you view or modify the resource configuration.
In the Name field, enter a name for the new instance or use the default.
Next to License, click the arrow to expand the license acceptance section.
Set License Accept to true if you accept the Cloud Pak for Integration license agreement. For details, see Licensing.
For License LI, leave the default version unless you change
spec.version
. For details about specific version licenses, see the "Table of license versions" section in LicensingSpecify 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.Set any other configuration values as appropriate.
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
Update the values in the file:
For
metadata.namespace
, select your project (namespace) name.For
spec.license.accept
, selecttrue
if you accept the Cloud Pak for Integration license. agreement. For details, see Licensing.For
spec.license
, keep the default value unless you change the value forspec.version
. For details about specific version licenses, consult the "Table of license versions" section in Licensing.- For
spec.storage.class
, specify a file storage class that supports ReadWriteMany (RWX) volumes and allows read and write access to non-root users. Supported storage providers includeibmc-file-gold-gid
, OpenShift Data Foundation (formerly OpenShift Container Storage), Spectrum, and Portworx. For additional details about storage support and configuration, see Storage considerations.Tip: You can get a current list of available storage classes by clicking the Form View tab, then clicking the dropdown for Select Storage Class. Click Create. You are redirected to the Platform UI tab.
To verify that the Platform UI is being created, click the name of the instance created in the list. At the end of the page in the Conditions section, the Type should be
Pending
. In up to 40 minutes, this value should change toReady
.Your instance of Cloud Pak for Integration is added to the list of instances in the current project (namespace).
Logging in to the Platform UI
When the Platform UI status changes to Ready
, log in to the Platform UI for the first time to create users and permissions.
In the OpenShift web console, click the application menu icon, and under IBM Cloud Paks, click the Platform UI instance you want to access.
If certificates have not been configured, you may need to accept the certificates to get to the login screen.
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. See Getting the initial admin password in the next section.
The Platform UI opens.
Getting the initial admin password
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), complete these steps:
Log in to the OpenShift web console with your OpenShift cluster admin credentials. Make sure the Administrator perspective is selected.
In the navigation panel, click to expand Workloads, then select Secrets.
At the top of the Secrets pane, click the arrow to expand the Project list, and select
ibm-common-services
.To filter your options, enter
platform-auth-idp-credentials
in the search box, then clickplatform-auth-idp-credentials
in the list.Scroll down to the Data pane and copy the value for
admin_password
.Save the password to use when logging in to Platform UI.
Next steps
After you complete other deployment tasks in the Platform UI, you can perform additional post-installation configuration such as:
Managing users. For more information, see Adding users in the IBM Cloud Pak Platform UI and the other topics in the Identity and access management section.
Create additional admin users authenticated by your identity provider and change the initial admin credentials. For more information, see Changing the cluster administrator access credentials.
Configuring the foundational services. See Configuring Cloud Pak foundational services.
For additional tasks, see Administering.
After configuring the Platform UI, deploy IBM Cloud Pak for Integration capabilities. For more information, see Deploying instances of capabilities.