System requirements for required components
Required components provide required underlying functionality for IBM® Cloud Pak for Data services. Required cluster components describes when and how these components are installed. Ensure that you have sufficient resources to install the appropriate components on your cluster.
Required component support information
The information is provided in the following sections:
Version support
Use this table to determine which versions of a component are supported on the version of Cloud Pak for Data that you are running.
Component | Cloud Pak for Data Version 3.5 |
---|---|
Scheduling service |
|
IBM Cloud Pak for Data Common core services |
|
IBM Cloud Pak® foundational services Events Service | 0.20.x or later |
IBM Cloud Pak foundational services IAM Service | 3.x |
IBM Cloud Pak foundational services License Service | 1.2.3 or later |
Hardware requirements
Use this table to determine whether you have the minimum required resources to install the component on your Cloud Pak for Data cluster.
Keep the following information in mind as you review the hardware requirements:
- Unless explicitly stated, the component can be scheduled across existing worker nodes.
- If a component requires dedicated nodes, the documentation for the component describes how to prevent other components or services from running on those nodes.
Service | x86-64 | POWER® | Z | vCPU | Memory | Storage requirements | Notes |
---|---|---|---|---|---|---|---|
Common core services | ✓ | ✓ | 11 vCPU | 17.8 GB RAM | 500 GB Supported storage types:
|
If this component is needed, it is installed once in each project where Cloud Pak for Data is installed. The component is a dependency for multiple services. The first service that specifies the common core services as a dependency installs the component. The preceding resources are required in addition to the resources required for the service installation. |
|
Scheduling service | ✓ | ✓ | 4 vCPU | 10 GB RAM | 10 GB Supported storage types:
|
This component is installed once and is used by any instances of Cloud Pak for Data on the cluster. For details, see Setting up the scheduling service on your cluster. |
|
IBM Cloud Pak foundational services Events Service | ✓ | ✓ | ✓ | This information is not currently available. | This information is not currently available. | This information is not currently available. | This component is installed once and is used by any instances of Cloud Pak for Data on the cluster. See the IBM Cloud Pak foundational services documentation for more information: |
IBM Cloud Pak foundational services IAM Service | ✓ | ✓ | ✓ | This information is not currently available. | This information is not currently available. | This information is not currently available. | This component is installed once and is used by any instances of Cloud Pak for Data on the cluster. See the IBM Cloud Pak foundational services documentation for more information: |
IBM Cloud Pak foundational services License Service | ✓ | ✓ | ✓ | This information is not currently available. | This information is not currently available. | This information is not currently available. | This component is installed once and is used by any instances of Cloud Pak for Data on the cluster. See the IBM Cloud Pak foundational services documentation for more information:
|
Software dependencies
Component | External dependencies | Service dependencies |
---|---|---|
Common core services |
None |
None |
Scheduling service |
None |
None |
IBM Cloud Pak foundational services Events Service |
None |
Not applicable |
IBM Cloud Pak foundational services IAM Service |
None |
Not applicable |
IBM Cloud Pak foundational services License Service |
None |
Not applicable |
Multitenancy support
With the exception of the IBM Cloud Pak for Data common core services, which are installed once in a given project (namespace), the required components are installed once on a Red Hat® OpenShift cluster. The services are shared by any instances of Cloud Pak for Data on the cluster.