Preparing for a starter deployment

Red Hat OpenShift Kubernetes Service (ROKS) cluster and a private OpenShift cluster have different requirements. Make sure that the client can connect to the cluster you want to use and download the cert-kubernetes repository.

Download the cert-kubernetes repository.

1. Go to the Container Application Software for Enterprises (CASE) package URL.
2. Extract the package.
3. Extract the contents from the .tar file in the ibm-cp-automation/inventory/cp4aOperatorSdk/files/deploy/crs folder. Use the tar -xvzf command to extract the archives.

   tar -xvzf ibm-cp-automation-5.0.0.tgz
   cd ibm-cp-automation/inventory/cp4aOperatorSdk/files/deploy/crs
   tar -xvf cert-k8s-23.0.1.tar

Note: Releases with interim fixes are packaged in archives with a new minor version. The version numbers follow the release.major.minor standard. For example, the first interim fix for 23.0.1 is packaged in the archive ibm-cp-automation-5.0.1.tgz. To find the latest interim fix for 23.0.1 and the associated CASE package, go to the interim fix readme file.

Server-side requirements

Table 1. Server-side requirements step by step

Requirement	More information
Get your IBM entitlement key	Log in to MyIBM Container Software Library with the IBMid and password that is associated with the entitled software. In the Container software library tile, verify your entitlement on the View library page, and then go to Get entitlement key to retrieve the key.
Check capacity	The administrator must make sure that the target cluster has the capacity for all of the capabilities that you plan to install. For more information, see System requirements.
A namespace	Warning: If you plan to use a project (namespace) that you used previously for another Cloud Pak for Business Automation deployment (starter or production), delete all the related PVCs before you install a new starter deployment. On the left panel in your OpenShift console, click Administration > Namespaces, then click Create Namespace. In the Create Namespace dialog, specify a name for the namespace, for example cp4ba-starter. To use the default Network Policy, make sure you select "No restrictions". Note: If you plan to use the "All namespaces" option to install the Cloud Pak operator, then the openshift-operators namespace is used. You still need a namespace to create a CP4BA deployment, so go ahead and create one.
A service account	Create the ibm-cp4ba-anyuid service account (SA) in a service-account-for-starter.yaml file. apiVersion: v1 kind: ServiceAccount metadata: name: ibm-cp4ba-anyuid imagePullSecrets: - name: "ibm-entitlement-key" Apply the service account to the target namespace. oc apply -f service-account-for-starter.yaml -n ${NAMESPACE} Where the ${NAMESPACE} is the namespace where you want to install the deployment. Bind the security context constraints (SCC) to control the actions the SA can take and what it can access. oc adm policy add-scc-to-user anyuid \ -z ibm-cp4ba-anyuid -n ${NAMESPACE}
Synchronize worker nodes clocks	Cloud Pak for Business Automation requires that the clocks on the worker nodes are synchronized. An OCP cluster that is installed in a restricted network is configured to use a public Network Time Protocol (NTP) server by default. To avoid clock skew, reconfigure the cluster to use a private NTP server instead. Time synchronization must be enabled on all hosts in the cluster, whether using NTP or any other method. For more information, see Configuring chrony time service.

It is also worth noting the following information:

• If you want to install Business Automation Insights, then specific services from the Cloud platform foundation are needed. The foundational services are installed by the Automation foundation operator.
• The "starter" deployment provisions PostgreSQL and OpenLDAP with the default values, so you do not need to prepare them in advance. The database is for internal purposes only and cannot be accessed.