Accelerate your IBM Cloud Pak journey with Red Hat OpenShift Container Platform accelerator 4.9.0.0 in IBM Cloud Pak System 2.3.3.4
IBM®Cloud Pak System is a system to help manage your resources in a cloud-computing environment.
IBM Cloud Pak System uses workload accelerators, also known as patterns, to create consistent, validated, and repeatable virtual applications within the cloud environment. Workload accelerators are solutions that enable the deployment of complex business applications in a cloud environment. When you use a workload pattern, you can focus on an application as opposed to the middleware infrastructure in which the application runs. Visit IBM® Cloud Pak System page to know more.
Red Hat OpenShift is an application platform product developed by Red Hat that enables software engineers to develop and deploy applications at scale. Built on top of Kubernetes and offering enterprise grade capabilities, OpenShift is a popular option for on-premises or hybrid cloud container-based architectures because it provides a fully-fledged Kubernetes cluster with the support level required by large organizations.
IBM Cloud Pak System accelerates your implementation of on-premises Kubernetes platforms. It comes with support for automated deployment and configuration of Red Hat OpenShift Container Platform (OCP). This factor makes it the perfect platform for on-premises deployment of IBM Cloud Paks and Red Hat OpenShift clusters!
This tutorial focuses on the deployment of Red Hat OpenShift Container Platform 4.9.0 in IBM Cloud Pak System V2.3.3.4(Intel platform). For information about Version 4.6, refer to the IBM Community article Deploying Red Hat OpenShift 4.6 on IBM Cloud Pak System.
What's new in Red Hat OpenShift Container Platform accelerator 4.9.0.0 in IBM Cloud Pak System 2.3.3.4:
- IBM Red Hat OpenShift Acceleration pattern 4.9.0.0 supports deployment of four different versions of Red Hat OpenShift Container Platform.
Table 1 shows the different Red Hat OpenShift Container Platform versions that are supported by IBM Cloud Pak System 2.3.3.4 .
| Accelerator version |
Red Hat OpenShift Container Platform version |
| 4.9.0.0 |
4.9.0 |
| 4.8.12 |
| 4.7.31 |
| 4.6.35 |
Table 1
- IBM catalog is enabled out-of-box (OOB) for online Red Hat OpenShift Container Platform deployments, by using IBM OpenShift Acceleration pattern 4.9.0.0 in IBM Cloud Pak System 2.3.3.4. This factor enables quick deployment of IBM Cloud Paks in IBM Cloud Pak System.
Prerequisites
Before you deploy your first Red Hat OpenShift Container Platform 4.9 cluster on IBM Cloud Pak System, few prerequisites need to be in place. For a good starting point on these prerequisites, see IBM Documentation at https://www.ibm.com/docs/en/cloud-pak-system?topic=4900-system-requirements:
- IBM Cloud Pak System 2.3.3.4 Intel-based IBM Cloud Pak System models W3500, W3550, and W4600 are supported. There is currently no support for the Power based IBM Cloud Pak System models.
- IBM OS image for Red Hat Linux Systems (RHEL 8.4 X64) Version 8.4, IBM OS image for Red Hat Linux Systems (RHEL 7.9 X64) Version 7.9 and Red Hat Container Platform OpenShift accelerator 4.9.0.0 - It uses Red Hat Enterprise Linux (RHEL) 8.4 as the default image. Scenarios using a custom OS image are also supported, as long as it is Red Hat Enterprise Linux (RHEL) 7.9 or higher.
- IBM OS image for Red Hat Enterprise Linux CoreOS Version 4.8.14 - This image is included with the Red Hat accelerator bundle for OpenShift Container Platform 4.9.0.0.
- Docker Accelerator 1.0.15.1 Docker registry is required for accessing Red Hat OpenShift Container Platform images for a disconnected installation. Obtain Docker registry accelerator 1.0.15.1 from IBM FixCentral.
- Red Hat OpenShift Container Platform accelerator 4.9.0.0 - Red Hat OpenShift Container Platform accelerator is used for deploying a Red Hat OpenShift Container Platform cluster in IBM Cloud Pak System. Get the Red Hat OpenShift Container Platform accelerator 4.9.0.0 from IBM FixCentral.
- Red Hat Satellite Server 6 shared service deployed -The shared service should be connected to an existing Red Hat Satellite Server (RHSS), or to RHSS deployed on IBM Cloud Pak System with access to the ansible-2.9-for-rhel-8-x86_64-rpms,rhel-8-for-x86_64-baseos-rpms,rhel-8-for-x86_64-appstream-rpms repositories.
- If you choose RHEL 7, enable access to the repositories rhel-7-server-rpms and rhel-7-server-extras-rpms repositories.
Note: IBM Cloud Pak System comes with Red Hat subscriptions for RHEL and RHSS.
- Active subscription with Red Hat for the OpenShift Container Platform - Unlike the Red Hat subscription for RHEL and RHSS, the Red Hat OpenShift Container Platform (OCP) subscription is not included with IBM Cloud Pak System. Please refer to OpenShift Container Platform accelerator V4.3.1.0 recipe for detailed steps.
- Sufficient compute, memory, and storage resources on IBM Cloud Pak System - A single Red Hat OpenShift Container Platform cluster requires at least 28 virtual CPUs, 112 GB of RAM, and 1202 GB of storage.
For detailed prerequisite steps to configure Red Hat Satellite Server, refer to OpenShift Container Platform accelerator V4.3.1.0 recipe
For detailed steps to configure Private Docker Registry on IBM Cloud Pak System, refer to (keep the video link here once available from Anshu)
Now we will see how to deploy Red Hat OpenShift Container Platform in IBM Cloud Pak System
Load and verify required artifacts on IBM Cloud Pak System V2.3.3.4
Refer to Table 2 for complete list of content that you need :
Table 2
The “IBM Cloud Pak System accelerator bundle for Red Hat OpenShift Container Platform V4.9.0” is not installed by default. To confirm, log in to IBM Cloud Pak System and go to System > Storehouse Browser. If you do not see an entry for /admin/files/RedHatOpenShift as shown in Figure 1, it means that the binaries are not installed yet.
Figure 1
Process for loading the binaries has been documented at https://www.ibm.com/docs/en/cloud-pak-system?topic=bundles-importing-openshift-container-platform-accelerator-bundle
./cloudpakimport.sh
***************************************************
Cloud Pak Accelerator Bundle Import utility
***************************************************
Artifacts from accelerator Bundle will be imported to Cloud Pak System
Cloud Pak System hostname or IP address: 9.42.98.77
Cloud Pak System username: admin
Password for admin:
- Testing connectivity to Cloud Pak System
Upload Cloud Pak binaries to Storehouse
-----------------------------------------------
- Uploading binaries for: Red Hat OpenShift 4.9.0 on IBM Cloud Pak System
- Pre-upload Verification
1) ocp4.9.0-x86_64.tgz: found locally but not on server
2) ocp4.8.12-x86_64.tgz: verified successfully
3) openshift-client-linux-4.6.45.tar.gz: verified successfully
4) openshift-install-linux-4.8.12.tar.gz: verified successfully
5) ocp4.6.45-x86_64.tgz: verified successfully
6) openshift-client-linux-4.8.12.tar.gz: verified successfully
7) openshift-install-linux-4.9.0.tar.gz: found locally but not on server
8) openshift-install-linux-4.7.31.tar.gz: verified successfully
9) openshift-client-linux-4.9.0.tar.gz: verified successfully
10) openshift-client-linux-4.7.31.tar.gz: verified successfully
11) openshift-install-linux-4.6.45.tar.gz: verified successfully
12) jq-linux64: verified successfully
13) ocp4.3.1-x86_64-extra.tar: verified successfully
14) ocp4.7.31-x86_64.tgz: verified successfully
- Uploading ocp4.9.0-x86_64.tgz
- ocp4.9.0-x86_64.tgz uploaded
- ocp4.8.12-x86_64.tgz is already on the server
- openshift-client-linux-4.6.45.tar.gz is already on the server
- openshift-install-linux-4.8.12.tar.gz is already on the server
- ocp4.6.45-x86_64.tgz is already on the server
- openshift-client-linux-4.8.12.tar.gz is already on the server
- Uploading openshift-install-linux-4.9.0.tar.gz
- openshift-install-linux-4.9.0.tar.gz uploaded
- openshift-install-linux-4.7.31.tar.gz is already on the server
- openshift-client-linux-4.9.0.tar.gz is already on the server
- openshift-client-linux-4.7.31.tar.gz is already on the server
- openshift-install-linux-4.6.45.tar.gz is already on the server
- jq-linux64 is already on the server
- ocp4.3.1-x86_64-extra.tar is already on the server
- ocp4.7.31-x86_64.tgz is already on the server
- Post-upload verification
1) ocp4.9.0-x86_64.tgz: verified successfully
2) ocp4.8.12-x86_64.tgz: verified successfully
3) openshift-client-linux-4.6.45.tar.gz: verified successfully
4) openshift-install-linux-4.8.12.tar.gz: verified successfully
5) ocp4.6.45-x86_64.tgz: verified successfully
6) openshift-client-linux-4.8.12.tar.gz: verified successfully
7) openshift-install-linux-4.9.0.tar.gz: verified successfully
8) openshift-install-linux-4.7.31.tar.gz: verified successfully
9) openshift-client-linux-4.9.0.tar.gz: verified successfully
10) openshift-client-linux-4.7.31.tar.gz: verified successfully
11) openshift-install-linux-4.6.45.tar.gz: verified successfully
12) jq-linux64: verified successfully
13) ocp4.3.1-x86_64-extra.tar: verified successfully
14) ocp4.7.31-x86_64.tgz: verified successfully
- All binaries verified successfully.
- Verifying file
Name: IBM_OS_Image_for_Red_Hat_Enterprise_Linux_CoreOS_16G_4_8_14.ova
- Downloading CLI from Cloud Pak System
- Starting Cloud Pak System CLI
OpenJDK 64-Bit Server VM warning: You have loaded library /tmp/jna3611880720913081135.tmp which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
/
Import and Clone Virtual Images
----------------------------------------
- Checking for Virtual Image
Name: IBM OS Image for Red Hat Linux Systems
Version: 4.0.0.0
- Virtual Image is available
- Working with image
Name: IBM OS Image for Red Hat Enterprise Linux CoreOS - 16G
Version: 4.8.14
- Virtual Image will be imported from
IBM_OS_Image_for_Red_Hat_Enterprise_Linux_CoreOS_16G_4_8_14.ova
- Waiting for import to finish. This would take few minutes.
- Cloning the image
Name: IBM OS Image for Red Hat Enterprise Linux CoreOS - 120G
- Waiting for clone to finish
- Image import completed for IBM_OS_Image_for_Red_Hat_Enterprise_Linux_CoreOS_16G_4_8_14.ova
Import Ptypes
------------------------
- Import ptype for: Red Hat OpenShift 4.9.0 on IBM Cloud Pak System
- Working with ptype
Name: openshift
Version: 4.9.0.0
- Ptype exists. Skipping the Ptype import
Confirm that the following files are now visible from the IBM Cloud Pak System. Go to Problem Determination> Storehouse Browser and confirm that you see what is shown in Figure 2.
Figure 2
The new and improved IBM Cloud Pak accelerator bundle import utility is available for Red Hat OpenShift Container Platform V4.6.0.0 and higher accelerator on IBM Cloud Pak System. It loads images to storehouse, clones the Red Hat Enterprise Linux CoreOS OVA to two variants with different disk size of 16 GB and 120 GB, and makes them available in IBM Cloud Pak System Virtual Images catalog as shown in Figure 3. In addition, it also imports the accelerator into IBM Cloud Pak System.
Figure 3
- Verify and import Pattern Types
The new and improved IBM Cloud Pak accelerator bundle import utility (described in previous step) for IBM Cloud Pak System loads the pattern type to IBM Cloud Pak System too. After it is loaded, you should see the Red Hat OpenShift Container Platform 4.9.0.0 accelerator in the catalog with the available status as shown in Figure 4.
Figure 4
- Explore Red Hat OpenShift Container Platform 4 cluster accelerator
Go to Provision accelerators from the IBM Cloud Pak System user interface as shown in Figure 5
Figure 5
Search for OpenShift Container Platform and click Ready to deploy as shown in Figure 6.
Figure 6
This action opens a page to select Default or Customized cluster.
Select Customized as shown in Figure 7 and click Continue. The Configure deployment page opens.
Figure 7
The first section in this page includes IBM Cloud Pak System deployment options as shown in Figure 8. For example, environment profile, cloud group, and so on. Select the appropriate values such that all prerequisites are available in the chosen cloud group.
Figure 8
The second section in this page contains OS users root and virtuser credentials for helper virtual machines as shown in Figure 9.
Figure 9
The last section in this page includes an optional parameter to generate SSH key, which is used in deployment as shown in Figure 10. If you generate this key, you can use it to connect to helper and Red Hat OpenShift Container Platform virtual machines via SSH.
Figure 10
Click Configure nodes to open the Configure nodes tab page.
This page shows the type of virtual machines (VMs), such as helpers, control planes and worker nodes, which are included in the accelerator and hardware resource configuration for each virtual machine as shown in Figure 11 and Figure 12. You can change the resource configuration of all nodes in a cluster to be deployed. Use slider, as shown in Figure 11, to set the desired value for each resource type of virtual machines.
Note: Once done, the required node configurations, switch off the "Advanced" slider button before moving to the next tab.
Figure 11
Note: You cannot change number of masters to be deployed as Red Hat recommends deploying three masters for Red Hat OpenShift Container Platform 4 clusters.
Figure 12
Click OpenShift options to open the OpenShift options tab page.
This page shows deployment parameters for Red Hat OpenShift Container Platform accelerator as shown in Figures 13 and 14. Detailed description of parameters can be found here.
OpenShift version
It is the Red Hat OpenShift Container Platform version to deploy.
Note: To deploy Red Hat OpenShift Container Platform version other than 4.9.0, change value in this field. Refer to Table 1 for supported versions of Red Hat in IBM Cloud Pak System 2334.
OpenShift cluster domain name
It is the domain name for Red Hat OpenShift Container Platform cluster. If not specified, then a default cluster domain name is generated.
OpenShift cluster name
It is the Red Hat OpenShift Container Platform cluster name. If not specified, then a default cluster name is generated.
OpenShift image registry name
It is the fully qualified name for the Red Hat OpenShift Container Platform image registry. In case there is no IBM Cloud Pak System Registry available in cloud group or you wish to use a different docker registry for accessing Red Hat OpenShift Container Platform images, specify registry hostname:port here.
OpenShift image registry username
It is the username needed to access the Red Hat OpenShift Container Platform secure image registry.
OpenShift image registry password
It is the user password that is needed to access the Red Hat OpenShift Container Platform secure image registry.
OpenShift pull-secret
If access to external OpenShift registry is available and you wish to use it for Red Hat OpenShift Container Platform images, paste contents of the downloaded OpenShift install pull-secret.json file here.
Figure 13
Alternate NFS server name or IP address (for the OpenShift image registry)
It is the alternate NFS server name or IP address of the OpenShift image registry. By default, the Primary helper virtual machine is used to configure storage for OpenShift image registry. If this parameter value is specified, then this external NFS server is used for OpenShift image registry instead. Please see this page about configuring NFS server and path.
Alternate NFS server path (for the OpenShift image registry)
It is the alternate NFS server path of the OpenShift image registry. It is used along with the Alternate NFS server name or IP address parameter to configure storage for OpenShift image registry.
Alternate NFS server name or IP address (for the application persistent storage)
It is the alternate NFS server name or IP address of the Application Persistent Storage. By default Primary helper is used to configure persistent storage for workloads to be deployed on Red Hat OpenShift Container Platform cluster. When value is specified here, it is used for persistent storage for workloads instead.
Alternate NFS server path (for the application persistent storage)
It is the alternate NFS server path of the Application Persistent Storage. It is used along with Alternate NFS server name or IP address parameter to configure persistent storage for workloads.
Figure 14
Click Review and deploy to open the Ready to deploy tab page. This page shows a summary of topology and resource configuration as shown in Figure 15.
Figure 15
Following is a brief description of various nodes that are included in this cluster.
PrimaryHelper and SecondaryHelper
There are two Helper nodes that run on RHEL 8.4. They support the deployment of OpenShift cluster on virtual machines that run Red Hat Core OS. The Helper node provides services for the OpenShift Cluster as documented in the OpenShift 4 documentation: Helper Git Repository and Helper Blog. IBM implements two Helper virtual machines and uses a floating IP address to provide high availability for these services.
Bootstrap
There is one Bootstrap node that is used to install the Red Hat OpenShift Container Platform control plane on the master nodes. It is only used during the bootstrapping of Red Hat OpenShift Container Platform. Eventually, this virtual machine is destroyed and resources are released.
Master
There are three master nodes deployed on virtual machines that run on Red Hat Core OS. OpenShift 4 requires three master nodes, ensuring high availability and quorum of essential Kubernetes services like etcd.
Worker
By default, there are two worker nodes deployed on virtual machines that run on Red Hat Core OS. This factor ensures high availability of containers that run on these worker nodes. Depending on the needs for your OpenShift cluster, you could opt for a higher number of worker nodes or worker nodes with more CPU and memory. Starting from IBM Cloud Pak System V2.3.3.0, it is possible to add additional worker nodes to your OpenShift cluster after deployment (horizontal scaling).
As shown in the following table, by default, single OCP cluster requires 28 virtual CPUs, 112 GB of RAM, and 1202 GB of storage. Depending on the number and sizing of the worker nodes, the amount of resources required could be higher.
| VM |
Number |
OS |
virtual CPUs |
RAM (GB) |
storage (GB) |
|
Primary Helper
|
1
|
RHEL 8.4
|
4
|
16
|
470
|
|
Secondary Helper
|
1
|
RHEL 8.4
|
4
|
16
|
12
|
|
Bootstrap
|
1
|
RH Core OS 4.8.14
|
4
|
16
|
120
|
|
Master
|
3
|
RH Core OS 4.8.14
|
4
|
16
|
120
|
|
Worker
|
2
|
RH Core OS 4.8.14
|
2
|
8
|
120
|
|
Total
|
8
|
–
|
28
|
112
|
1202
|
Note: IBM catalog is enabled out-of-box (OOB) for online installations. OOB IBM catalog is enabled to deploy any IBM Cloud Pak quickly.
- Deployment of Red Hat OpenShift Container Platform 4 cluster
With all the previous steps completed, you are now ready to deploy your first Red Hat OpenShift 4.9 cluster!
Go to the Cloud Pak System user interface (https://<ICPS_system_IP>/cps/) and log in. The Getting started page opens up. Click Provision accelerators as shown in Figure 16.
Figure 16
The Provision accelerators page opens up. Search for OpenShift Container Platform and click Ready to deploy as shown in Figure 17.
Figure 17
Users can deploy OpenShift Container Platform with default or customized configuration.
You should see a page as shown in Figure 18. By default, Red Hat OpenShift Container Platform version is set to 4.9.0.
Figure 18
Select Default or Customized option based on your requirement.
Default deployment
Default deployment option deploys an Red Hat OpenShift Container Platform cluster with already configured values with minimum hardware Red Hat OpenShift Container Platform cluster. To deploy default cluster, select Default as shown in Figure 19.
Figure 19
Customized deployment
Customized deployment enables you to configure the cluster as per business use case. It provides a way to change hardware specification for the Red Hat OpenShift Container Platform cluster to be deployed. To deploy a customized cluster, select Customized as shown in Figure 20 and click Continue.
Figure 20
If you want the customized deployment steps, refer to section Exploring Red Hat OpenShift 4 cluster accelerator section of this article. If you want to do a default deployment, continue with this procedure.
Click Continue to open the Configure deployment page as shown in Figure 21.
The first section on this page shows environment profile, cloud group, and IP group for deployment. Select appropriate values based on where the RHUS and IBM Cloud Pak System registry shared services are running.
Figure 21
In Helper node credentials section, specify password for root and virtuser as shown in Figure 22.
Figure 22
Optionally, in the Optional section as shown in Figure 23, specify a SSH key to connect to helper virtual machines via SSH post deployment. If not specified, then a default key is generated and used.
Figure 23
Click Review and deploy.
Review the cluster topology and other values.
Click Deploy as shown in Figure 24 to deploy cluster.
Figure 24
Within some seconds, you should see a message indicating that the deployment has started as shown in Figure 25.
Figure 25
In the message box, click Manage accelerator instances . You will be redirected to Manage accelerator instances page. As shown in Figure 26, deployment starts with the cluster status in Launching state.
Figure 26
It takes approximately 50 minutes to deploy the Red Hat OpenShift Container Platform cluster. After it is deployed, you should see an instance as shown in Figure 27.
Figure 27
Review History section of the instance for post deployment actions as highlighted in Figure 28.
Figure 28
Post deployment actions
Before you can use the OpenShift 4 cluster, a few more steps are required as documented in step 6 of Getting started with OpenShift Container Platform 4.x pattern.
Review the History section for next steps as indicated in Figure 27.
- Retrieve the password for kubeadmin
The kubeadmin password gets generated during the installation of OpenShift 4. Retrieve the kubeadmin password by providing root password for Helper virtual machine as shown in Figure 29.
Figure 29
- Configure your DNS server
Set up the following two DNS wildcard entries for the floating IP address and fully-qualified domain name of your OpenShift 4 Virtual System Instance. This is required to access the Red Hat OpenShift Container Platform web-console, applications, and APIs.
*.<fqdn> IN A <ip>
*.apps.<fqdn> IN A <ip>
In the case of our OpenShift 4 cluster here, the floating IP address is ocp_cluster_ip with the corresponding fully-qualified domain name cps-r81-9-46-123-56.xxx.xxx.xxx.xxx . Therefore, you need to configure the following DNS wildcard entries:
*.apps.cps-r81-9-46-123-56.xxx.xxx.xxx.xxx IN A x.xx.xx.56
*.cps-r81-9-46-123-56.xxx.xxx.xxx.xxx IN A x.xx.xx.56
If you are unable to easily make changes to your DNS server, you can add the following entries to your local /etc/hosts file (or equivalent on Windows) for testing purposes. This will allow you to log in to the Red Hat OpenShift Container Platform web console, but note that you would need additional entries for any applications that you would deploy later.
ocp_cluster_ip console-openshift-console.apps.cps-r81-9-46-123-56.xxx.xxx.xxx.xxx oauth-openshift.apps.cps-r81-9-46-123-56.xxx.xxx.xxx.xxx
You can find more information about OpenShift external DNS requirements here. The DNS records listed as “This record must be resolvable by both clients external to the cluster …” are required. DNS is also provided on the Helper Nodes to cover the resolution inside the cluster.
If you are able to configure DNS records up front, then the cluster console link will be accessible immediately. Configuring DNS ahead of time is the recommended approach for deploying Red Hat OpenShift Container Platform clusters on IBM Cloud Pak System. You would need to create the following records in your DNS server for each IP in the IP group you are using to deploy (so that any IP that is selected from the IP group to be the floating IP for the cluster will already have wildcard entries associated with it in DNS):
*.sub.domain IN A <ip>
*.mycluster.sub.domain IN A <ip>
- Access your Red Hat OpenShift cluster
You can now access your OpenShift 4 cluster using the Red Hat OpenShift Container Platform web console link as shown in Figure 30.
Figure 30
Log in with the username kubeadmin and the password that you retrieved earlier as shown in Figure 31.
Figure 31
After you log in, you will see the console as shown in Figure 32.
Figure 32
Verify the IBM Operator Catalog is enabled (for online deployment only)
Go to Operators > OperatorHub and observe ibm-operator-catalog enabled as shown in Figure 33
Figure 33
Go to Compute > Nodes. If you see three master nodes and two worker nodes, then it confirms that the OpenShift 4 cluster topology was deployed as expected.
- Verify your OpenShift cluster
Inspect your cluster from IBM Cloud Pak Console -> Manage accelerator instances
In the IBM Cloud Pak Console -> Manage accelerator instances page, click Nodes for the deployed instance as shown in Figure 34. You can verify the cluster topology and virtual machines that are deployed as part of the instance.
Figure 34
In the IBM Cloud Pak System user interface, go to -> Manage accelerator instances, click Middleware for the deployed instance as shown in Figure 35. You can verify the cluster topology and deployed virtual machines as a part of the instance.
Figure 35
Note: Do not stop or restart the Red Hat OpenShift Container Platform cluster or any nodes until after 24 hours of deployment. Failing to do so may render your cluster to a broken state that cannot be recovered. Refer this page for more information.
Register your Red Hat OpenShift cluster with Red Hat
Finally, do not forget to register your OpenShift cluster with Red Hat. This manual step is required if your OpenShift cluster does not have internet access to reach Red Hat. You can follow step 4 here to register your cluster on the “Cluster registration” page.
Next steps
Now you are ready for day 2 operations and workload deployment on your Red Hat OpenShift Container Platform cluster. See this article for day 2 Red Hat OpenShift Container Platform cluster operations in IBM Cloud Pak System.
Next, you can quickly deploy IBM Cloud Pak of your choice with few simple clicks. For detailed steps refer to this article.
Conclusion
IBM Cloud Pak System 2.3.3.4 enables clients to quickly roll out one or more Red Hat OpenShift 4.9.x, 4.8.x, 4.7.x, 4.6.x clusters, which greatly simplifies the process, ensures consistency, and avoids human error. This is also used as the foundation for the deployment of IBM Cloud Paks on the IBM Cloud Pak System platform.
I would like to thank Anshu Garg and Anilkumar Hedge for their help in writing this article.