Installing shared cluster components for IBM Cloud Pak for Data

Important: IBM Cloud Pak for Data Version 4.8 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.

Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.8 reaches end of support. For more information, see Upgrading from IBM Cloud Pak for Data Version 4.8 to IBM Software Hub Version 5.1.

Before you install IBM Cloud Pak for Data, you must install the IBM Cloud Pak foundational services Certificate manager and License Service. You can optionally install the Cloud Pak for Data scheduling service.

Installation phase

Setting up a client workstation

Setting up a cluster

Collecting required information

Preparing to run installs in a restricted network

Preparing to run installs from a private container registry

Preparing the cluster for Cloud Pak for Data

Preparing to install an instance of Cloud Pak for Data

Installing an instance of Cloud Pak for Data

Who needs to complete this task?

Cluster administrator A cluster administrator must complete this task.

You can optionally give another user the minimum role-based access control to install the scheduling service. However, this method requires additional planning and maintenance and is not recommended for typical installations. For more information, see Giving a user the minimum RBAC to install the scheduling service.

When do you need to complete this task?

One-time setup You must complete this task before you install Cloud Pak for Data for the first time.

Before you begin

Best practice: You can run the commands in this task exactly as written if you set up environment variables. For instructions, see Setting up installation environment variables.

Ensure that you source the environment variables before you run the commands in this task.

About this task

The following components are cluster-wide components, which means that they are installed once and shared by all instances of Cloud Pak for Data on the cluster.

Cluster-wide component Notes

Cluster-wide component	Notes
Certificate manager	A certificate manager is required. The IBM Cloud Pak foundational services Certificate manager is recommended over the Red Hat® OpenShift® `cert-manager` or a community certificate manager. However, if the `cpd-cli` detects another certificate manager on the cluster, it will not install the IBM Cloud Pak foundational services Certificate manager.
License Service	The IBM Cloud Pak foundational services License Service is required. You are required to keep a record of the size of your deployments to report to IBM as requested. If you are using Container Licensing, you can use the License Service to measure Cloud Pak for Data usage.
Scheduling service	The scheduling service is required if you plan to use: The quota enforcement feature in Cloud Pak for Data The node scoring feature for pod placement The Watson Machine Learning Accelerator service Priority scheduling and co-scheduling in the Analytics Engine powered by Apache Spark service If none of these scenarios applies to you, the scheduling service is optional but strongly recommended.

Certificate manager

A certificate manager is required.

The IBM Cloud Pak foundational services Certificate manager is recommended over the Red Hat® OpenShift® cert-manager or a community certificate manager. However, if the cpd-cli detects another certificate manager on the cluster, it will not install the IBM Cloud Pak foundational services Certificate manager.

License Service

The IBM Cloud Pak foundational services License Service is required.

You are required to keep a record of the size of your deployments to report to IBM as requested. If you are using Container Licensing, you can use the License Service to measure Cloud Pak for Data usage.

Scheduling service

The scheduling service is required if you plan to use:

The quota enforcement feature in Cloud Pak for Data
The node scoring feature for pod placement
The Watson Machine Learning Accelerator service
Priority scheduling and co-scheduling in the Analytics Engine powered by Apache Spark service

If none of these scenarios applies to you, the scheduling service is optional but strongly recommended.

Procedure

Log the cpd-cli in to the Red Hat OpenShift Container Platform cluster:
```
${CPDM_OC_LOGIN}
```
Remember: CPDM_OC_LOGIN is an alias for the cpd-cli manage login-to-ocp command.
Install the Certificate manager and the License Service:
Tip: Before you run this command against your cluster, you can preview the oc commands that this command will issue on your behalf by running the command with the --preview=true option.
The oc commands are saved to the preview.sh file in the work directory.
```
cpd-cli manage apply-cluster-components \
--release=${VERSION} \
--license_acceptance=true \
--cert_manager_ns=${PROJECT_CERT_MANAGER} \
--licensing_ns=${PROJECT_LICENSE_SERVICE}
```
Wait for the cpd-cli to return the following message before proceeding to the next step:
```
[SUCCESS]... The apply-cluster-components command ran successfully.
```
Install the scheduling service:
Tip: Before you run this command against your cluster, you can preview the oc commands that this command will issue on your behalf by running the command with the --preview=true option.
The oc commands are saved to the preview.sh file in the work directory.
```
cpd-cli manage apply-scheduler \
--release=${VERSION} \
--license_acceptance=true \
--scheduler_ns=${PROJECT_SCHEDULING_SERVICE}
```
Wait for the cpd-cli to return the following message before proceeding to the next step:
```
[SUCCESS]... The apply-scheduler command ran successfully.
```

What to do next

Now that you've installed the shared cluster components, you're ready to complete Configuring persistent storage for IBM Cloud Pak for Data.