Creating projects (namespaces) on Red Hat OpenShift Container Platform
Before you install IBM® Cloud Pak for Data on Red Hat® OpenShift® Container Platform, a cluster administrator should create the OpenShift projects (Kubernetes namespaces) where you plan to deploy the Cloud Pak for Data software.
About this task
The projects that you need to create depend on several factors.
Factors | Planning considerations | Security considerations |
---|---|---|
The number of Cloud Pak for Data instances you plan to install | By default, most services are installed in the same project as the Cloud Pak for Data control plane. If you want to install multiple
instances of Cloud Pak for Data on a single cluster, you
must create a project for each instance of Cloud Pak for Data that you plan to install. Review the documentation for the services that you plan to deploy to determine whether you need to create any additional projects on Red Hat OpenShift Container Platform. For details, see Services and integrations. |
The cluster administrator uses the cpd-cli adm command with the
--apply flag to make the following changes to the project:
Alternatively, the cluster administrator can use the YAML files that
are generated by the For details, see Setting up the cluster for the control plane. |
Whether you plan to install services that can run in tethered projects | A few services can be installed in tethered projects. A tethered project is
managed by the Cloud Pak for Data control plane but is
otherwise isolated from Cloud Pak for Data and the other
services that are installed in that project. For information on which services can be installed in tethered projects, see Multitenancy support in System requirements for services. |
The cluster administrator uses the cpd-cli adm command with the
--apply flag and the --tether-to flag to grant the RBAC for
the Cloud Pak for Data control plane to manage deployments
in the tethered project.For details, see the appropriate service installation documentation. |
Whether you plan to install the scheduling service |
You must install the scheduling service if you plan to use:
The scheduling service is installed once on the cluster and
can be used by all instances of Cloud Pak for Data on the
cluster.
Do not install this service in the same project as the Cloud Pak for Data control plane or other Cloud Pak for Data services. It is recommended that you install the scheduling service in one of the following projects:
For details, see Installing prerequisite required components. When you run the |
The cluster administrator uses the cpd-cli adm command with the
--apply flag to make the following changes to the project:
Alternatively, the cluster administrator can use the YAML files that
are generated by the For details, see Setting up the cluster for the scheduling service. |
Whether you plan to install the Cloud Pak for Data Operator |
The Cloud Pak for Data Operator is not required or recommended for all
environments. Install the Cloud Pak for Data Operator
only if one or more of the following situations applies to you:
cpd-cli ) to install the Cloud Pak for Data control plane and services. The Cloud Pak for Data Operator is installed once on the cluster and
can be used by all instances of Cloud Pak for Data.
It is recommended that you install the Cloud Pak for Data Operator in a project named
For details, see Installing prerequisite required components. |
By default, the Cloud Pak for Data Operator:
However, a cluster administrator can override this behavior by creating the following
configmap before they install the Cloud Pak for Data control plane:
The cluster administrator can then use the the
YAML files that are generated by the cpd-cli adm preview
command to manually apply the RBAC and SCC changes.For details, see Setting up the cluster for the control plane. |
Whether you plan to install the IBM Cloud Pak foundational services | You can install the following IBM Cloud Pak foundational services on your Red Hat OpenShift Container Platform:
It is recommended
that you install these services in a project called For details, see Integrating with Cloud Pak foundational services. |
Follow the guidance in the IBM Cloud Pak foundational services documentation. For details, see Security context constraints. |