Setting up the cluster with the admin script
To install the Cloud Pak capabilities with the Cloud Pak operator, a cluster administrator user must run a script to set up the cluster. They also need to provide a non-administrator user the information that they need to be able to run the deployment script. Each Cloud Pak capability can be installed with extra components. Postgres and OpenLDAP are always installed.
Before you begin
Make sure that you prepared your cluster with the necessary infrastructure and software. For more information, see Preparing for a starter deployment.
About this task
The cluster setup script is one of several scripts that are provided to help you install the Cloud Pak capabilities. You must be a cluster administrator to run the setup script. For more information, see user archetypes.
The cluster setup script identifies or creates a namespace and applies the custom resource definitions (CRD). The script provides the administrator with the cluster hostname on the cluster and available storage classes. This information must be provided to the user who runs the deployment script.
A new installation of Cloud Pak for Business Automation always includes a namespace-scoped instance of foundational services when you use the scripts.
Use the following steps to complete the set up.
Procedure
Results
When the script is finished, the available storage class names are displayed along with the infrastructure node name. Take a note of the following information and provide it to the Cloud Pak admin user as they are needed for the deployment script:
- Project name or namespace.
- Storage class names.
- Username to log in to the cluster.
Verify the deployment to make sure that all pods are Running. Using the OpenShift CLI:
oc get pods
To get the operator log, run the following commands:
oc project <namespace of Cloud Pak for Business Automation operator>
NAMESPACE=$(oc project -q)
oc get pod | grep ibm-cp4a-operator | awk '{print $1}'
The command returns two pod names. The ibm-cp4a-operator-catalog
and one that
has a suffix of around ten and then five characters, for example,
ibm-cp4a-operator-696d8d9555-27qrf
. Use the pod name that is not the catalog in the
following command.
podname=$(oc get pod | grep ibm-cp4a-operator-696d8d9555-27qrf | awk '{print $1}')
oc logs $podname -c operator -n $NAMESPACE
A ClusterServiceVersion (CSV) for the operators appear in the target namespace, and APIs provided by the operators are available to use. Run the following command to get the CSVs:
oc get csv -n $NAMESPACE
What to do next
Go to and complete the next step in Installing the capabilities by running the deployment script.