Shared components

Shared components provide underlying functionality for the IBM Cloud Pak® for Data control plane and services. IBM Cloud Pak for Data uses two types of shared components: cluster-wide components and instance-level components.

Cluster-wide components

The cluster-wide components are installed exactly once on the cluster and are shared by all instances of Cloud Pak for Data on the cluster.

Shared cluster-wide components are different from end-user services, such as the Watson™ Studio or Watson Query services. Unlike services, end users do not interact directly with the shared cluster-wide components.

Instance-level components

The instance-level components are installed once in each instance of Cloud Pak for Data. For example, if you have 5 instances of Cloud Pak for Data on the cluster, you also have 5 instances of the instance-level components.

Some of the instance-level components provide features that end-users interact with directly.

Cluster-wide components

Use the following information to determine which cluster-wide components you must install on your cluster.

Component Features Required if...

Component	Features	Required if...
IBM® Certificate manager	The IBM Certificate manager service, provides centralized certificate management with automatic certificate rotation.	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 License Service measures your use of Cloud Pak for Data. You can use the service to generate audit snapshots of your use.	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 offers enhancements over the default Kubernetes scheduler, such as: Advanced pod placement logic Resource sharing Quota logic Pod co-scheduling Pod prioritization	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.

IBM® Certificate manager

The IBM Certificate manager service, provides centralized certificate management with automatic certificate rotation.

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 License Service measures your use of Cloud Pak for Data. You can use the service to generate audit snapshots of your use.

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 offers enhancements over the default Kubernetes scheduler, such as:

Advanced pod placement logic
Resource sharing
Quota logic
Pod co-scheduling
Pod prioritization

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.

Instance-level components

Use the following information to determine which instance-level components you must install.

Component	Features	Required if...
IBM Cloud Pak foundational services	The IBM Cloud Pak foundational services provide features that are used by IBM Cloud Paks, such as the Identity Management Service (Identity Management Service). The IBM Cloud Pak foundational services also enable the Cloud Pak for Data instance to integrate with the cluster-wide IBM Certificate manager and License Service.	The IBM Cloud Pak foundational services are required.
Cloud Pak for Data control plane	The Cloud Pak for Data control plane provide the central user experience for Cloud Pak for Data users and administrators. The control plane includes interfaces for: Creating and accessing service instances Managing users Configuring and customizing the web client Monitoring the health and resource use for the platform Creating and managing storage volumes The control plane also provides a way for users to access the services that are installed on the platform.	The Cloud Pak for Data control plane is required.
Cloud Pak for Data common core services	The common core services provide features that are used by multiple Cloud Pak for Data services. The features include: Connections Flight service Deployment management Job management Notifications Projects Search Metadata repositories	The Cloud Pak for Data common core services are required if you install a service that relies on the common core services. The common core services are automatically installed by the services that require them. If you install or upgrade a service that requires the common core services and the common core services are not installed or are not at the required level, the service will install or upgrade them. If you install or upgrade a service that requires the common core services and the common core services are already installed at the required level, the service will use the existing installation.

Component

Features

Required if...

IBM Cloud Pak foundational services

The IBM Cloud Pak foundational services provide features that are used by IBM Cloud Paks, such as the Identity Management Service (Identity Management Service).

The IBM Cloud Pak foundational services also enable the Cloud Pak for Data instance to integrate with the cluster-wide IBM Certificate manager and License Service.

The IBM Cloud Pak foundational services are required.

Cloud Pak for Data control plane

The Cloud Pak for Data control plane provide the central user experience for Cloud Pak for Data users and administrators.

The control plane includes interfaces for:

Creating and accessing service instances
Managing users
Configuring and customizing the web client
Monitoring the health and resource use for the platform
Creating and managing storage volumes

The control plane also provides a way for users to access the services that are installed on the platform.

The Cloud Pak for Data control plane is required.

Cloud Pak for Data common core services

The common core services provide features that are used by multiple Cloud Pak for Data services. The features include:

Connections
Flight service
Deployment management
Job management
Notifications
Projects
Search
Metadata repositories

The Cloud Pak for Data common core services are required if you install a service that relies on the common core services.

The common core services are automatically installed by the services that require them.

If you install or upgrade a service that requires the common core services and the common core services are not installed or are not at the required level, the service will install or upgrade them.
If you install or upgrade a service that requires the common core services and the common core services are already installed at the required level, the service will use the existing installation.