Deploying a Cloud Pak accelerator on OpenShift Container Platform

Prerequisites and steps to deploy Cloud Pak® accelerators on OpenShift Container Platform V4.x.

If any of the following prerequisites are done already as a part of your Cloud Pak accelerator 4.x prerequisite, then skip and proceed to the next step:

Ensure that a Red Hat Satellite Six Shared Service instance is available with the following packages:
- rhel-7-server-rpms
- rhel-7-server-extras-rpms
Note:
- These packages are used only by the Helper node.
- OpenShift Container Platform RPMs are not needed in the Red Hat Satellite Server for OpenShift V4.x. For more information about Red Hat Satellite Server setup, see https://developer.ibm.com/tutorials/accelerate-your-red-hat-openshift-container-platform-deployment-with-ibm-cloud-pak-system/#prepare-red-hat-satellite-server.
Deploy a IBM Cloud Pak Docker Private Registry Shared Service where OpenShift Container Platform V4.2.18 images are hosted:
1. Deploy an IBM Cloud Pak Docker Private Registry virtual system accelerator, which automatically loads the OpenShift Container Platform V4.2.18 images. Save the Fully Qualified Domain Name (FQDN) of this deployment for the next step.
2. Deploy the IBM Cloud Pak System Registry Service shared service in the cloud group where you plan to deploy OpenShift Container Platform clusters. When you deploy the IBM Cloud Pak System Registry Service shared service, enter the FQDN of the Cloud Paks Docker Private Registry accelerator that got deployed in the previous step.
Optionally, set up a DNS wildcard addresses for each of the IPs in the IP group that are used to deploy OpenShift Container Platform clusters. You can access the console immediately by using the console links on the IBM Cloud Pak System user interface. If DNS is not set up in advance, then you can do the following steps:
1. For testing purposes, add entries to /etc/hosts from the system that runs the web browser.
2. Add DNS entries individually after the OpenShift Container Platform installation is complete. For each IP address in the IP group used for OpenShift Container Platform deployments, add the following two wildcard entries:
```
*.<fqdn> IN A <ip>
*.apps.<fqdn> IN A <ip>
```
  Note: After the deployment completes, instructions are available in the History section of the user interface. For example, if this FQDN entry exists in your DNS:
```
9.9.9.9 cps-rack-79-vm-83.rtp.raleigh.ibm.com
```
  Add these two wildcard entries:
```
*.cps-rack-79-vm-83.rtp.raleigh.ibm.com IN A 9.9.9.9        
*.apps.cps-rack-79-vm-83.rtp.raleigh.ibm.com IN A 9.9.9.9
```
  For more information about OpenShift external DNS requirements, https://docs.openshift.com/container-platform/4.2/installing/installing_vsphere/installing-restricted-networks-vsphere.html#installation-dns-user-infra_installing-restricted-networks-vsphere.. The DNS records listed as "This record must be resolvable by both clients external to the cluster ..." are required. DNS is provided on the Helper Nodes to cover the resolution inside the cluster.
Deploy the accelerator after the prerequisites are complete.