Setting up the cluster by running a script

For more information about downloading cert-kubernetes, see Option 1: Preparing your cluster for an online deployment.

cd ${PATH_TO_EXTRACTED_FILES}/cert-kubernetes/scripts

./cp4a-clusteradmin-setup.sh 

1. From 23.0.2-IF005 Select the CP4BA deployment environment: Online (1) / Offline or Airgap (2). Select Online.
2. Select the platform type: ROKS (1) or OCP (2).
3. Select the deployment type production.
4. If you plan to enable FIPS for your Cloud Pak for Business Automation deployment, select Yes to check that the worker nodes on the cluster are FIPS enabled.

   If you are installing IBM Business Automation Insights Extension in a version earlier than 23.0.2 interim fix IF003, select No because IBM Business Automation Insights does not support FIPS.

   Note: If all the compute nodes are FIPS enabled, then the script creates a configMap (cp4ba-fips-status) in the target deployment namespace (cp4ba-project for example) to record that FIPS is enabled.

   kind: ConfigMap
   apiVersion: v1
   metadata:
     name: cp4ba-fips-status
     namespace: <project_name>
   data:
     all-fips-enabled: 'Yes'

5. Select Yes if you want to install CP4BA as a private catalog rather than in the global catalog namespace (GCN). The GCN uses the openshift-marketplace namespace, the private option uses the target namespace of your CP4BA deployment. The default is No.

   When you select Yes to enable a private catalog, enter the name of the namespace (cp4ba-project) for the target deployment, and then choose an existing user on your cluster, a non-admin user is recommended. For more information, see Preparing a namespace for the operator. If an existing CP4BA operator is found in another namespace on your cluster, confirm that you want to deploy another CP4BA operator in the new namespace by entering Yes. You must install a CP4BA operator in each namespace where you want to install a CP4BA deployment.

6. Enter Yes or No to confirm whether you want to use the images in the IBM Entitlement Registry.
7. If you replied Yes to use the IBM Entitlement Registry, enter your IBM Entitled Registry key and login credentials (user and password).

   If you want to load the container images to a local registry, then set up the cluster by mirroring the images instead of running the cp4a-clusteradmin-setup.sh script. For more information, see Setting up the cluster and use a local image registry.

   Tip: If you ran the cp4a-clusteradmin-setup.sh script and you see one or more of the following messages, then make sure that you start Docker or Podman and run the script again.

   Error saving credentials: error storing credentials
   Error: unable to connect
   The Entitlement Registry key failed

oc get pod -w

oc project <namespace of Cloud Pak for Business Automation operator>
NAMESPACE=$(oc project -q)
podname=$(oc get pod -n $NAMESPACE | grep ibm-cp4a-operator | awk '{print $1}')
oc logs $podname -f

You can also list the ClusterServiceVersion (CSV) to verify the version of the running operators on your cluster.

oc get csv -n $NAMESPACE

If you set any subscriptions to manual, then you must approve any pending operator updates. It is not recommended to set subscriptions to manual because it can make the installation error prone when some of the dependency operators are not approved. By default, all subscriptions are set to automatic.

oc get installPlan