Setting up the cluster
If you plan to use the Form view in Operator Hub, then set up the cluster with the OpenShift console. You can also use the admin script to set up the cluster.
About this task
You can install multiple Cloud Pak for Business Automation production deployments on the same cluster. When you have multiple deployments on a cluster, the Cloud Pak foundational services are namespace-scoped by default, but can be shared between them. You cannot set up an Red Hat OpenShift cluster that has both cluster-scoped foundational services and namespace-scoped instances.
To use a namespace-scoped instance of foundational services, you must create or update the
common-service-maps configMap before you start installing your Cloud Pak for Business Automation and foundational
services instances.
When you use a shared instance of foundational services, the user repositories are also shared in the common Identity and Access Management (IAM) service. If you use multiple LDAPs with IAM, you must make sure that the usernames are unique across them. Your Cloud Pak for Business Automation deployments can either use the same LDAP or make sure that your users are unique. For more information, see Configuring LDAP connection.
openshift-operators
namespace to find installed operators. If Automation foundation operators are already installed by
another Cloud Pak in All namespaces on the cluster, then you must install Cloud Pak for Business Automation in All
namespaces on the cluster. The only way that you can install a new Cloud Pak for Business Automation deployment in
All Namespaces is by using the OpenShift console and making sure that the cluster
does not have a common-service-maps configMap. Using the scripts on a cluster that
does not have an existing instance of foundational services, then you can install foundational
services only in a namespace-scoped instance.