Hardware requirements for x86_64 clusters

Before you install IBM Software Hub on an x86_64 cluster, review the hardware requirements for IBM Software Hub, the shared cluster components, and the services that you plan to install.

Components	Related links
IBM Software Hub platform hardware requirements	Review the minimum requirements for a stable installation. Work with your IBM Sales representative to determine whether you need more resources based on: The shared cluster components that you need to install. The services that you plan to install. The types of workloads that you plan to run.
Shared cluster-wide components	Review the hardware requirements for the shared cluster components that you need to install.
Instance-level prerequisites	Review the hardware requirements for the instance-level prerequisites.
Services	Review the hardware requirements for the services that you plan to install. Not all services are supported on all hardware.
Automatically installed dependencies	Review the hardware requirements for the automatically installed dependencies, such as the common core services. (These components are installed only if you install a service with a dependency on the component.)

IBM Software Hub platform hardware requirements

You must install IBM Software Hub on a Red Hat® OpenShift® Container Platform cluster. For information about the supported versions of Red Hat OpenShift Container Platform, see Software requirements.

It is strongly recommended that you deploy IBM Software Hub on a highly available cluster. If you plan to install IBM Software Hub on a highly available cluster, review Highly available deployments.
If high availability is not a requirement for your deployment, you can deploy IBM Software Hub on a single node OpenShift (SNO) cluster. If you plan to install IBM Software Hub on SNO, review Single node OpenShift deployments.

Highly available deployments

The following requirements are the minimum recommendations for a small, stable deployment of IBM Software Hub.

Sizing your cluster

Use the minimum recommended configuration as a starting point for your cluster configuration. If you use fewer resources, you are likely to encounter stability problems.

Important: Work with your IBM Sales representative to size your cluster.

The size of your cluster depends on multiple factors.

The shared components that you need to install.
The services that you plan to install.
The sizing requirements for services are available in Services. If you install only a few services with small vCPU and memory requirements, you might not need additional resources. However, if you plan to install multiple services or services with large footprints, add the appropriate amount of vCPU and memory to the minimum recommendations.
The types of workloads that you plan to run.
For example, if you plan to run complex analytics workloads in addition to other resource-intensive workloads, such as ETL jobs, you can expect reduced concurrency levels if you don't add additional computing power to your cluster.

Because workloads vary based on several factors, use measurements from running real workloads with realistic data to size your cluster.

For additional information on sizing your cluster, download the component scaling guidance PDF.

Choosing a configuration

The following configuration has been tested and validated by IBM. However, Red Hat OpenShift Container Platform supports other configurations. If the configuration in the following table does not work in your environment, you can adapt the configuration based on the guidance in the Red Hat OpenShift documentation.

Node role	Number of servers	Minimum available vCPU	Minimum memory	Minimum storage
Control plane	3 (for high availability)	4 vCPU per node (This configuration supports up to 24 worker nodes.)	16 GB RAM per node (This configuration supports up to 24 worker nodes.)	No additional storage is needed for IBM Software Hub. See the Red Hat OpenShift Container Platform documentation for sizing guidance.
Infra	3 (recommended)	4 vCPU per node (This configuration supports up to 27 worker nodes.)	24 GB RAM per node (This configuration supports up to 27 worker nodes.)	See the Red Hat OpenShift Container Platform documentation for sizing guidance.
Worker (compute)	2 worker nodes (minimum) 3 or more worker nodes (recommended)	8 vCPU per node (minimum) 16 vCPU per node (recommended)	64 GB RAM per node (minimum) 128 GB RAM per node (recommended)	300 GB of storage space per node for storing container images locally. If you plan to install watsonx.ai™, increase the storage to 500 GB per node. See IBM Software Hub platform storage requirements for details.
Load balancer	2 load balancer nodes (For development, test, or proof-of-concept clusters, you can use 1 load balancer node.)	2 vCPU per node	4 GB RAM per node Add another 4 GB of RAM for access restrictions and security control.	Add 100 GB of root storage for access restrictions and security control. A load balancer is required when using three control plane nodes. The load balancer can either be in the cluster or external to the cluster. However, in a production-level cluster, an enterprise-grade external load balancer is recommended.

Single node OpenShift deployments

You can use single node OpenShift (SNO) if redundancy and scalability are not a concern.

SNO might be a reasonable alternative to a multi-node, highly-available cluster in the following situations:

You are planning a small deployment with a limited number of services
You want to set up satellite or disconnected deployments that are connected to a larger deployment of IBM Software Hub
You plan to run workloads on remote physical locations
You want to set up ephemeral instances of IBM Software Hub for test pipelines
You need a cluster for demonstrations, training, or proof-of-concept installations.

Considerations

Before you choose an SNO deployment, ensure that you understand the following limitations of a single node deployment:

Limited scalability

SNO is not as scalable as a multi-node deployment. You might experience performance issues if you try to run too many applications on a single node.

Limited capacity

SNO has a limited capacity for storage and memory. You might need to upgrade your hardware to accommodate larger workloads.

Single point of failure

Because SNO runs on a single node, it is more susceptible to downtime in the event of a hardware failure.

Limited storage support

If you want to use SNO, you must use one of the following types of persistent storage:

NFS
Amazon Elastic storage, specifically Amazon Elastic File System and Amazon Elastic Block Store

Dedicated nodes are not supported

You cannot use dedicated nodes on an SNO cluster.

Best practices

If you decide to proceed with an SNO deployment, ensure that you adhere to the following best practices:

Workload planning: If you plan to run multiple applications on the cluster, ensure that you have sufficient capacity for the workloads that you plan to run. If you run a resource intensive workload, it might prevent other workloads from running on the cluster.
Backup and recovery: Implement a robust data protection strategy to help ensure that the system can be recovered quickly in the event of a disaster or system crash. See Backing up and restoring IBM Software Hub for information about supported backup methods.

Sizing your cluster

Use the minimum recommended configuration as a starting point for your cluster configuration. If you use fewer resources, you are likely to encounter stability problems.

Important: Work with your IBM Sales representative to size your cluster.

The size of your cluster depends on multiple factors.

The services that you plan to install.
The sizing requirements for services are available in Services. If you install only a few services with small vCPU and memory requirements, you might not need additional resources. However, if you plan to install multiple services or services with large footprints, add the appropriate amount of vCPU and memory to the minimum recommendations.

Best practice: Size your SNO cluster appropriately before deploying any software on the cluster. You will encounter performance issues if you have insufficient hardware.
The types of workloads that you plan to run.
For example, if you plan to run complex analytics workloads in addition to other resource-intensive workloads, such as ETL jobs, you can expect reduced concurrency levels if you don't add additional computing power to your cluster.

Because workloads vary based on several factors, use measurements from running real workloads with realistic data to size your cluster.

Best practice: If you plan to run multiple applications on the cluster, ensure that you have sufficient capacity for the workloads that you plan to run. If you run a resource intensive workload, it might prevent other workloads from running on the cluster.

For additional information on sizing your cluster, download the component scaling guidance PDF.

Choosing a configuration

The recommended configuration uses two virtual machines (VMs) that act as:

A bastion node with NFS storage configured
A worker (compute) node

VM role	Minimum available vCPU	Minimum memory	Minimum storage
Bastion node	4 vCPU	8 GB RAM	Allocate a minimum of 500 GB of disk space. The disk can be: In the same disk as the general bastion node storage. In a separate disk on the bastion node. On external storage.
Worker (compute)	16 vCPU	64 GB RAM	Allocate a minimum of 300 GB of disk space on the node for image storage. See IBM Software Hub platform storage requirements for details.

Shared cluster-wide components

Shared cluster components provide underlying functionality for the IBM Software Hub control plane and services. Use the following sections to understand the hardware requirements for the following components.

IBM Certificate manager
License Service
Scheduling service

For more information, see Cluster-wide components.

Use the following information to determine whether you have the minimum required resources to install each component on your cluster.

IBM Certificate manager

The IBM Certificate manager is supported for upgrades only.

vCPU	Memory	Storage	Notes
1.6 vCPU	1.94 GB RAM	This information is not currently available.	A certificate manager is required. This software is installed once on the cluster. For more information, see Cluster-wide components. Review the Hardware requirements and recommendations for foundational services in the IBM Cloud Pak foundational services documentation for updates to the hardware requirements: Version 4.13 Version 4.14

License Service

vCPU	Memory	Storage	Notes
3.1 vCPU	0.735 GB RAM	This information is not currently available.	Required. This software is installed once on the cluster. For more information, see Cluster-wide components. Review the Hardware requirements and recommendations for foundational services in the IBM Cloud Pak foundational services documentation for updates to the hardware requirements: Version 4.13 Version 4.14

Scheduling service

vCPU	Memory	Storage	Notes
Operator pods: 0.2 vCPU Catalog pods: 0.01 vCPU Operand: Up to 0.9 vCPU	Operator pods: 0.54 GB RAM Catalog pods: 0.05 GB RAM Operand: 3.65 GB RAM	Persistent storage: Not applicable Ephemeral storage: 0.9 GB Image storage: Up to 2.69 GB	Required in some situations, but generally recommended. This software is installed once on the cluster. For more information, see Cluster-wide components. Minimum resources for an installation with a single replica per service.

vCPU

Memory

Storage

Notes

Operator pods:
0.2 vCPU

Catalog pods:
0.01 vCPU

Operand:
Up to 0.9 vCPU

Operator pods:
0.54 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
3.65 GB RAM

Persistent storage:
Not applicable

Ephemeral storage:
0.9 GB

Image storage:
Up to 2.69 GB

Required in some situations, but generally recommended.

This software is installed once on the cluster. For more information, see Cluster-wide components.

Minimum resources for an installation with a single replica per service.

Instance-level prerequisites

Instance-level prerequisites provide underlying functionality for services. Use the following sections to understand the hardware requirements for:

IBM Software Hub
IBM Cloud Pak foundational services

For more information, see Instance-level components.

Use the following information to determine whether you have the minimum required resources to install each component on your cluster.

IBM Software Hub

vCPU	Memory	Storage	Notes
The requirements for the control plane are included in the IBM Software Hub platform hardware requirements.	The requirements for the control plane are included in the IBM Software Hub platform hardware requirements.	The requirements for the control plane are included in the IBM Software Hub platform hardware requirements.	Required. The control plane is installed once for each instance of IBM Software Hub on the cluster.

vCPU

Memory

Storage

Notes

The requirements for the control plane are included in the IBM Software Hub platform hardware requirements.

Required.

The control plane is installed once for each instance of IBM Software Hub on the cluster.

IBM Cloud Pak foundational services

vCPU	Memory	Storage	Notes
4 vCPU	5 GB RAM	See the Hardware requirements and recommendations for foundational services in the IBM Cloud Pak foundational services documentation: Version 4.13 Version 4.14	Required. The IBM Cloud Pak foundational services are installed once for each instance of IBM Software Hub on the cluster.

vCPU

Memory

Storage

Notes

4 vCPU

5 GB RAM

See the Hardware requirements and recommendations for foundational services in the IBM Cloud Pak foundational services documentation:

Required.

The IBM Cloud Pak foundational services are installed once for each instance of IBM Software Hub on the cluster.

Services

Use the following information to determine whether you have the minimum required resources to install each service that you want to use.

AI Factsheets

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Catalog pods: 0.01 vCPU Operand: 0.3 vCPU	Operator pods: 0.256 GB RAM Catalog pods: 0.05 GB RAM Operand: 1.2 GB RAM	Persistent storage: Uses the persistent storage provisioned by the common core services. Ephemeral storage: 300 GB Image storage: Up to 2.01 GB	Minimum resources for an installation with a single replica per service.

Anaconda Repository for IBM Cloud Pak for Data

vCPU	Memory	Storage	Notes
4 vCPU	8 GB RAM	1 TB	This service cannot be installed on your Red Hat OpenShift cluster. For details, see the Anaconda installation requirements.

Analytics Engine powered by Apache Spark

vCPU Memory Storage Notes

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Catalog pods: 0.01 vCPU Operand: 2.3 vCPU	Operator pods: 0.256 GB RAM Catalog pods: 0.05 GB RAM Operand: 9 GB RAM	Persistent storage:This information is not currently available. Ephemeral storage: 50 GB per vCPU request (SSDs are recommended) Image storage: Up to 65.53 GB	Spark jobs use `emptyDir` volumes for temporary storage and shuffling. If your Spark jobs use a lot of disk space for temporary storage or shuffling, make sure that you have sufficient space on the local disk where `emptyDir` volumes are created. The recommended location is a partition in /var/lib. For more information, see Understanding ephemeral storagein the Red Hat OpenShift documentation: Version 4.12 Version 4.14 Version 4.15 Version 4.16 Version 4.17 Version 4.18 Version 4.19 If you don't have sufficient space on the local disk, Spark jobs might run slowly and some of the executors might evict jobs. A minimum of 50 GB of temporary storage for each vCPU request is recommended. Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload. All of the Analytics Engine powered by Apache Spark service instances associated with an instance of IBM Software Hub use the same pool of resources.

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
2.3 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
9 GB RAM

Persistent storage:This information is not currently available.

Ephemeral storage:
50 GB per vCPU request
(SSDs are recommended)

Image storage:
Up to 65.53 GB

Spark jobs use emptyDir volumes for temporary storage and shuffling. If your Spark jobs use a lot of disk space for temporary storage or shuffling, make sure that you have sufficient space on the local disk where emptyDir volumes are created.

The recommended location is a partition in /var/lib. For more information, see Understanding ephemeral storagein the Red Hat OpenShift documentation:

If you don't have sufficient space on the local disk, Spark jobs might run slowly and some of the executors might evict jobs. A minimum of 50 GB of temporary storage for each vCPU request is recommended.

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

All of the Analytics Engine powered by Apache Spark service instances associated with an instance of IBM Software Hub use the same pool of resources.

Cognos Analytics

vCPU	Memory	Storage	Notes
Operator pods: 0.5 vCPU Catalog pods: 0.01 vCPU Operand: 9.6 vCPU	Operator pods: 1 GB RAM Catalog pods: 0.05 GB RAM Operand: 40 GB RAM	Persistent storage: 500 MB for the service 2 GB per instance (smallest instance) Ephemeral storage: 1 GB for the service 25.6 GB per instance (smallest instance) Image storage: Up to 14.73 GB	Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload. When you provision the Cognos Analytics service, you specify the size of the instance. The information here is for the smallest instance. For other sizes, see Provisioning the Cognos Analytics service.

vCPU

Memory

Storage

Notes

Operator pods:
0.5 vCPU

Catalog pods:
0.01 vCPU

Operand:
9.6 vCPU

Operator pods:
1 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
40 GB RAM

Persistent storage:

500 MB for the service
2 GB per instance (smallest instance)

Ephemeral storage:

1 GB for the service
25.6 GB per instance (smallest instance)

Image storage:
Up to 14.73 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

When you provision the Cognos Analytics service, you specify the size of the instance.

The information here is for the smallest instance. For other sizes, see Provisioning the Cognos Analytics service.

Cognos Dashboards

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Catalog pods: 0.5 vCPU Operand: 11 vCPU	Operator pods: 0.256 GB RAM Catalog pods: 0.256 GB RAM Operand: 36 GB RAM	Persistent storage: 30 GB Ephemeral storage: 37.4 GB Image storage: Up to 14.96 GB	Minimum resources for an installation with a single replica per service.

Data Gate

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Catalog pods: 0.01 vCPU Operand: 2 vCPU per instance	Operator pods: 0.1 GB RAM Catalog pods: 0.05 GB RAM Operand: 13 GB RAM per instance	Persistent storage: 50 GB per instance Ephemeral storage: 0.6 - 3.25 GB Image storage: Up to 18.21 GB	Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload.

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
2 vCPU per instance

Operator pods:
0.1 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
13 GB RAM per instance

Persistent storage:
50 GB per instance

Ephemeral storage:
0.6 - 3.25 GB

Image storage:
Up to 18.21 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

Data Privacy

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Catalog pods: 0.01 vCPU Operand: 9.9 vCPU	Operator pods: 0.256 GB RAM Catalog pods: 0.05 GB RAM Operand: 36 GB RAM	Persistent storage: Uses the persistent storage provisioned by IBM Knowledge Catalog. Ephemeral storage: 6 GB Image storage: Up to 2.45 GB	Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload.

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
9.9 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
36 GB RAM

Persistent storage:
Uses the persistent storage provisioned by IBM Knowledge Catalog.

Ephemeral storage:
6 GB

Image storage:
Up to 2.45 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

Data Product Hub

vCPU	Memory	Storage	Notes
Operator pods: 0.75–1.5 vCPU Catalog pods: 0.05–0.1 vCPU Operand: 2–16 vCPU	Operator pods: 1.5–3 GB RAM Catalog pods: 0.05–0.4 GB RAM Operand: 2–26 GB RAM	Persistent storage: 0–200 GB Ephemeral storage: 2–13 GB Image storage: Up to 2.37 GB	The number of resources depends on whether IBM Knowledge Catalog is already installed in this instance of IBM Software Hub: If IBM Knowledge Catalog is installed, you need fewer resources to install Data Product Hub. If IBM Knowledge Catalog is not installed, you need more resources to install Data Product Hub. Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload.

vCPU

Memory

Storage

Notes

Operator pods:
0.75–1.5 vCPU

Catalog pods:
0.05–0.1 vCPU

Operand:
2–16 vCPU

Operator pods:
1.5–3 GB RAM

Catalog pods:
0.05–0.4 GB RAM

Operand:
2–26 GB RAM

Persistent storage:
0–200 GB

Ephemeral storage:
2–13 GB

Image storage:
Up to 2.37 GB

The number of resources depends on whether IBM Knowledge Catalog is already installed in this instance of IBM Software Hub:

If IBM Knowledge Catalog is installed, you need fewer resources to install Data Product Hub.
If IBM Knowledge Catalog is not installed, you need more resources to install Data Product Hub.

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

Data Refinery

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Catalog pods: 0.5 vCPU Operand: 1 vCPU	Operator pods: 0.256 GB RAM Catalog pods: 1 GB RAM Operand: 4 GB RAM	Persistent storage: Uses the persistent storage provisioned by the common core services. Ephemeral storage: 2 GB Image storage: Up to 4.39 GB	Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload. This service is installed when you install IBM Knowledge Catalog or Watson Studio

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.5 vCPU

Operand:
1 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
1 GB RAM

Operand:
4 GB RAM

Persistent storage:
Uses the persistent storage provisioned by the common core services.

Ephemeral storage:
2 GB

Image storage:
Up to 4.39 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

This service is installed when you install IBM Knowledge Catalog or Watson Studio

Data Replication

vCPU	Memory	Storage	Notes
Operator pods: 0.5 vCPU Catalog pods: 0.01 vCPU Operand: 13 vCPU	Operator pods: 0.512 GB RAM Catalog pods: 0.05 GB RAM Operand: 14 GB RAM	Persistent storage: 10 GB - 512 GB Ephemeral storage: 22 GB Image storage: Up to 4.32 GB	Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload.

vCPU

Memory

Storage

Notes

Operator pods:
0.5 vCPU

Catalog pods:
0.01 vCPU

Operand:
13 vCPU

Operator pods:
0.512 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
14 GB RAM

Persistent storage:
10 GB - 512 GB

Ephemeral storage:
22 GB

Image storage:
Up to 4.32 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

DataStage

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Catalog pods: 0.01 vCPU Operand: 8 vCPU	Operator pods: 0.256 GB RAM Catalog pods: 0.05 GB RAM Operand: 31 GB RAM	Persistent storage: 300 GB Ephemeral storage: 10 GB - 25 GB Image storage: Up to 22.26 GB	Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload. Local storage in /var/lib/containers Adjust the amount of local storage per node based on the volume of data you are analyzing. Local storage should be approximately 2 times larger than the amount of data you expect the system to process concurrently.

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
8 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
31 GB RAM

Persistent storage:
300 GB

Ephemeral storage:
10 GB - 25 GB

Image storage:
Up to 22.26 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

Local storage in /var/lib/containers: Adjust the amount of local storage per node based on the volume of data you are analyzing. Local storage should be approximately 2 times larger than the amount of data you expect the system to process concurrently.

Data Virtualization

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Catalog pods: 0.01 vCPU Operand: 12 vCPU	Operator pods: 0.256 GB RAM Catalog pods: 0.05 GB RAM Operand: 38 GB RAM	Persistent storage: 280 GB total (assuming defaults) Head pod: 50 GB (default) One worker pod: 50 GB (default) Caching storage: 100 GB (default) Caching metadata: 10 GB Scheduling pod: 10 GB Log storage: 30 GB per pod Ephemeral storage: 2.428 - 13GB Image storage: Up to 2.98 GB	Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload. When you provision the service, you can specify: The size of the persistent volume for the head pod The size of the persistent volume for the cache The number of worker pods The size of the persistent volume for the worker pods

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
12 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
38 GB RAM

Persistent storage:
280 GB total (assuming defaults)

Head pod:
50 GB (default)
One worker pod:
50 GB (default)
Caching storage:
100 GB (default)
Caching metadata:
10 GB
Scheduling pod:
10 GB
Log storage:
30 GB per pod

Ephemeral storage:
2.428 - 13GB

Image storage:
Up to 2.98 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

When you provision the service, you can specify:

The size of the persistent volume for the head pod
The size of the persistent volume for the cache
The number of worker pods
The size of the persistent volume for the worker pods

Db2

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Catalog pods: 0.01 vCPU Operand: 8 vCPU	Operator pods: 0.256 GB RAM Catalog pods: 0.05 GB RAM Operand: 24 GB RAM	Persistent storage: 540 GB (assuming defaults) Ephemeral storage: 2.2 - 10.2 GB Image storage: Up to 0.73 GB	Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload. A dedicated node is recommended for production deployments of Db2. For details, see Setting up dedicated nodes.

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
8 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
24 GB RAM

Persistent storage:
540 GB (assuming defaults)

Ephemeral storage:
2.2 - 10.2 GB

Image storage:
Up to 0.73 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

A dedicated node is recommended for production deployments of Db2. For details, see Setting up dedicated nodes.

Db2 Big SQL

vCPU	Memory	Storage	Notes
Operator pods: 0.2 vCPU Catalog pods: 0.1 vCPU Operand: 10.2 vCPU	Operator pods: 0.3 GB RAM Catalog pods: 0.2 GB RAM Operand: 66.7 GB RAM	Persistent storage: 470 GB total (assuming defaults) Head pod: 200 GB (default) One worker pod: 200 GB (default) Scheduling pod: 10 GB Log storage: 30 GB per pod Ephemeral storage: 1.4 - 12.2 GB Image storage: Up to 0.39 GB	Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload. When you provision the service, you can specify: The resources (vCPU and RAM) for the head and worker pods The number of worker pods The size of the persistent volume for the head pod and worker pods

vCPU

Memory

Storage

Notes

Operator pods:
0.2 vCPU

Catalog pods:
0.1 vCPU

Operand:
10.2 vCPU

Operator pods:
0.3 GB RAM

Catalog pods:
0.2 GB RAM

Operand:
66.7 GB RAM

Persistent storage:
470 GB total (assuming defaults)

Head pod:
200 GB (default)
One worker pod:
200 GB (default)
Scheduling pod:
10 GB
Log storage:
30 GB per pod

Ephemeral storage:
1.4 - 12.2 GB

Image storage:
Up to 0.39 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

When you provision the service, you can specify:

The resources (vCPU and RAM) for the head and worker pods
The number of worker pods
The size of the persistent volume for the head pod and worker pods

Db2 Data Management Console

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Catalog pods: 0.01 vCPU Operand: 5 vCPU	Operator pods: 0.256 GB RAM Catalog pods: 0.05 GB RAM Operand: 19.31 GB RAM	Persistent storage: 10 GB Ephemeral storage: 7.5 GB Image storage: Up to 6.09 GB	Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload. For information on sizing the provisioned instance, see Creating a service instance for Db2 Data Management Console from the web client.

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
5 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
19.31 GB RAM

Persistent storage:
10 GB

Ephemeral storage:
7.5 GB

Image storage:
Up to 6.09 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

For information on sizing the provisioned instance, see Creating a service instance for Db2 Data Management Console from the web client.

Db2 Warehouse

vCPU	Memory	Storage	Notes
Operator pods: 0.5 vCPU Catalog pods: 0.01 vCPU Operand: SMP: 7 vCPU MPP: 39 vCPU	Operator pods: 0.256 GB RAM Catalog pods: 0.05 GB RAM Operand: SMP: 98 GB RAM MPP: 610 GB RAM	Persistent storage: 540 GB (assuming defaults) Ephemeral storage: 2.2 - 11.3 GB Image storage: Up to 0.73 GB	Minimum resources for an installation with a single replica per service. Use dedicated nodes for: Production SMP deployments (recommended) MPP deployments (required) For detail, see Setting up dedicated nodes. Development deployment 1 node for SMP 2 nodes for MPP Production deployment 1 node for SMP 2-999 nodes for MPP Recommended configuration Work with IBM Sales to get a more accurate sizing based on your expected workload.

vCPU

Memory

Storage

Notes

Operator pods:
0.5 vCPU

Catalog pods:
0.01 vCPU

Operand:
SMP: 7 vCPU
MPP: 39 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
SMP: 98 GB RAM
MPP: 610 GB RAM

Persistent storage:
540 GB (assuming defaults)

Ephemeral storage:
2.2 - 11.3 GB

Image storage:
Up to 0.73 GB

Minimum resources for an installation with a single replica per service.

Use dedicated nodes for:

Production SMP deployments (recommended)
MPP deployments (required)

For detail, see Setting up dedicated nodes.

Development deployment

1 node for SMP
2 nodes for MPP

Production deployment

1 node for SMP
2-999 nodes for MPP

Recommended configuration

Work with IBM Sales to get a more accurate sizing based on your expected workload.

Decision Optimization

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Catalog pods: 0.01 vCPU Operand: 0.9 vCPU	Operator pods: 0.256 GB RAM Catalog pods: 0.05 GB RAM Operand: 1.5 GB RAM	Persistent storage: 12 GB Ephemeral storage: 300 - 6500 MB Image storage: Up to 3.76 GB	Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload.

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
0.9 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
1.5 GB RAM

Persistent storage:
12 GB

Ephemeral storage:
300 - 6500 MB

Image storage:
Up to 3.76 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

EDB Postgres

vCPU	Memory	Storage	Notes
Operator pods: IBM: 0.1 vCPU Third-party: 0.5 vCPU Catalog pods: 0.01 vCPU Operand: User-defined	Operator pods: IBM: 0.256 GB RAM Third-party: 0.2 GB RAM Catalog pods: 0.05 GB RAM Operand: User-defined	Persistent storage: 100 GB Ephemeral storage:This information is not currently available. Image storage: Up to 3.37 GB	Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload.

vCPU

Memory

Storage

Notes

Operator pods:
IBM: 0.1 vCPU
Third-party: 0.5 vCPU

Catalog pods:
0.01 vCPU

Operand:
User-defined

Operator pods:
IBM: 0.256 GB RAM
Third-party: 0.2 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
User-defined

Persistent storage:
100 GB

Ephemeral storage:This information is not currently available.

Image storage:
Up to 3.37 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

Execution Engine for Apache Hadoop

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Catalog pods: 0.01 vCPU Operand: For each deployment: 0.5 vCPU + (0.5 vCPU * number of Hadoop registrations) + (0.6 vCPU * number of Hadoop jobs run)	Operator pods: 0.256 GB RAM Catalog pods: 0.05 GB RAM Operand: For each deployment: 0.5 GB + (0.5 GB * number of Hadoop registrations) + (0.5 GB * number of Hadoop jobs run)	Persistent storage: 2 GB per image pushed Ephemeral storage: 218 - 436 MB Image storage: Up to 2.50 GB	Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload. Each image that is pushed to the remote Hadoop cluster requires disk space where image tgz file can be stored. Execution Engine for Apache Hadoop requires an Execution Engine for Hadoop RPM installation on the Apache Hadoop cluster. For details, see Installing the service on Apache Hadoop clusters.

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
For each deployment:
0.5 vCPU + (0.5 vCPU * number of Hadoop registrations) + (0.6 vCPU * number of Hadoop jobs run)

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
For each deployment:
0.5 GB + (0.5 GB * number of Hadoop registrations) + (0.5 GB * number of Hadoop jobs run)

Persistent storage:
2 GB per image pushed

Ephemeral storage:
218 - 436 MB

Image storage:
Up to 2.50 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

Each image that is pushed to the remote Hadoop cluster requires disk space where image tgz file can be stored.

Execution Engine for Apache Hadoop requires an Execution Engine for Hadoop RPM installation on the Apache Hadoop cluster. For details, see Installing the service on Apache Hadoop clusters.

IBM Knowledge Catalog

IBM Knowledge Catalog includes optional features. Review the sizing based on the features that you plan to enable.

Base service (required)

vCPU Memory Storage Notes

vCPU	Memory	Storage	Notes
Operator pods: 0.75 vCPU Catalog pods: 0.05 vCPU Operand: 36 vCPU	Operator pods: 1.5 GB RAM Catalog pods: 0.2 GB RAM Operand: 73 GB RAM	Persistent storage: 700 GB Ephemeral storage: 28 GB Image storage: Up to 46.95 GB with all optional components	The minimum required resources depend on the features that you install. The minimum requirements include the resource requirement for one dynamic Spark cluster. Local storage in /var/lib/containers Adjust the amount of local storage per node based on the volume of data you are analyzing. Local storage should be approximately 2 times larger than the amount of data you expect the system to process concurrently. Persistent storage The raw size of shared storage depends on the storage class you use. For example, if you use `portworx-shared-gp3`, which has 3 replicas, multiply the storage by the number of replicas.

Operator pods:
0.75 vCPU

Catalog pods:
0.05 vCPU

Operand:
36 vCPU

Operator pods:
1.5 GB RAM

Catalog pods:
0.2 GB RAM

Operand:
73 GB RAM

Persistent storage:
700 GB

Ephemeral storage:
28 GB

Image storage:
Up to 46.95 GB with all optional components

The minimum required resources depend on the features that you install.

The minimum requirements include the resource requirement for one dynamic Spark cluster.

Local storage in /var/lib/containers: Adjust the amount of local storage per node based on the volume of data you are analyzing. Local storage should be approximately 2 times larger than the amount of data you expect the system to process concurrently.
Persistent storage: The raw size of shared storage depends on the storage class you use. For example, if you use portworx-shared-gp3, which has 3 replicas, multiply the storage by the number of replicas.

Data quality (optional)

vCPU	Memory	Storage	Notes
Operand: 8 vCPU	Operand: 29 GB RAM	Persistent storage: Not applicable Ephemeral storage: 31 GB	No additional notes for this feature.

Relationship explorer and semantic search (optional)

vCPU	Memory	Storage	Notes
Operator pods: 0.75 vCPU Catalog pods: 0.05 vCPU Operand: 6 vCPU	Operator pods: 1.5 GB RAM Catalog pods: 0.2 GB RAM Operand: 10 GB RAM	Persistent storage: 213 GB Ephemeral storage: 3 GB	No additional notes for this feature.

IBM Knowledge Catalog Premium

IBM Knowledge Catalog Premium includes optional features. Review the sizing based on the features that you plan to enable.

Base service (required)

vCPU	Memory	Storage	Notes
Operator pods: 1.5 vCPU Catalog pods: 0.1 vCPU Operand: 36 vCPU	Operator pods: 3 GB RAM Catalog pods: 0.4 GB RAM Operand: 73 GB RAM	Persistent storage: 700 GB Ephemeral storage: 28 GB Image storage: Up to 28.66 GB	Minimum resources for an installation with a single replica per service. The minimum requirements include the resource requirement for one dynamic Spark cluster. Work with IBM Sales to get a more accurate sizing based on your expected workload.

vCPU

Memory

Storage

Notes

Operator pods:
1.5 vCPU

Catalog pods:
0.1 vCPU

Operand:
36 vCPU

Operator pods:
3 GB RAM

Catalog pods:
0.4 GB RAM

Operand:
73 GB RAM

Persistent storage:
700 GB

Ephemeral storage:
28 GB

Image storage:
Up to 28.66 GB

Minimum resources for an installation with a single replica per service.

The minimum requirements include the resource requirement for one dynamic Spark cluster.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

Data quality (optional)

vCPU	Memory	Storage	Notes
Operand: 8 vCPU	Operand: 29 GB RAM	Persistent storage: Not applicable Ephemeral storage: 31 GB	No additional notes for this feature.

Semantic automation running on CPU (optional)

You can use CPU or GPU to run the foundation models for this feature.

vCPU	Memory	Storage	Notes
Operand: 11 vCPU	Operand: 14 GB RAM	Persistent storage: 10 GB Ephemeral storage: 3 GB	For better performance, use GPU.

Semantic automation running on GPU (optional)

You can use CPU or GPU to run the foundation models for this feature. GPU offers better performance than CPU.

vCPU	Memory	Storage	Notes
Operand: 3 vCPU	Operand: 4 GB RAM	Persistent storage: 10 GB Ephemeral storage: 3 GB	This option requires 1 GPU. For more information about supported GPUs, see GPU requirements for models.

Semantic embedding (optional)

vCPU	Memory	Storage	Notes
Operand: 2 vCPU	Operand: 3 GB RAM	Persistent storage: Not applicable Ephemeral storage: 1 GB	This feature requires the semantic automation feature.

AI search (optional)

vCPU	Memory	Storage	Notes
Operand: 4 vCPU	Operand: 4 GB RAM	Persistent storage: Not applicable Ephemeral storage: 1 GB	No additional notes for this feature.

Relationship explorer and semantic search (optional)

vCPU	Memory	Storage	Notes
Operator pods: 0.75 vCPU Catalog pods: 0.05 vCPU Operand: 6 vCPU	Operator pods: 1.5 GB RAM Catalog pods: 0.2 GB RAM Operand: 10 GB RAM	Persistent storage: 213 GB Ephemeral storage: 3 GB	No additional notes for this feature.

IBM Knowledge Catalog Standard

IBM Knowledge Catalog Standard includes optional features. Review the sizing based on the features that you plan to enable.

Base service (required)

vCPU	Memory	Storage	Notes
Operator pods: 1.5 vCPU Catalog pods: 0.1 vCPU Operand: 36 vCPU	Operator pods: 3 GB RAM Catalog pods: 0.4 GB RAM Operand: 73 GB RAM	Persistent storage: 700 GB Ephemeral storage: 28 GB Image storage: Up to 28.66 GB	Minimum resources for an installation with a single replica per service. The minimum requirements include the resource requirement for one dynamic Spark cluster. Work with IBM Sales to get a more accurate sizing based on your expected workload.

vCPU

Memory

Storage

Notes

Operator pods:
1.5 vCPU

Catalog pods:
0.1 vCPU

Operand:
36 vCPU

Operator pods:
3 GB RAM

Catalog pods:
0.4 GB RAM

Operand:
73 GB RAM

Persistent storage:
700 GB

Ephemeral storage:
28 GB

Image storage:
Up to 28.66 GB

Minimum resources for an installation with a single replica per service.

The minimum requirements include the resource requirement for one dynamic Spark cluster.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

Semantic automation running on CPU (optional)

You can use CPU or GPU to run the foundation models for this feature.

vCPU	Memory	Storage	Notes
Operand: 11 vCPU	Operand: 14 GB RAM	Persistent storage: 10 GB Ephemeral storage: 3 GB	For better performance, use GPU.

Semantic automation running on GPU (optional)

You can use CPU or GPU to run the foundation models for this feature. GPU offers better performance than CPU.

vCPU	Memory	Storage	Notes
Operand: 3 vCPU	Operand: 4 GB RAM	Persistent storage: 10 GB Ephemeral storage: 3 GB	This option requires 1 GPU. For more information about supported GPUs, see GPU requirements for models.

Semantic embedding (optional)

vCPU	Memory	Storage	Notes
Operand: 2 vCPU	Operand: 3 GB RAM	Persistent storage: Not applicable Ephemeral storage: 1 GB	This feature requires the semantic automation feature.

AI search (optional)

vCPU	Memory	Storage	Notes
Operand: 4 vCPU	Operand: 4 GB RAM	Persistent storage: Not applicable Ephemeral storage: 1 GB	No additional notes for this feature.

Relationship explorer and semantic search (optional)

vCPU	Memory	Storage	Notes
Operator pods: 0.75 vCPU Catalog pods: 0.05 vCPU Operand: 6 vCPU	Operator pods: 1.5 GB RAM Catalog pods: 0.2 GB RAM Operand: 10 GB RAM	Persistent storage: 213 GB Ephemeral storage: 3 GB	No additional notes for this feature.

IBM Manta Data Lineage

vCPU	Memory	Storage	Notes
Operator pods: 0.75–1.5 vCPU Catalog pods: 0.05–0.1 vCPU Operand: 12–24 vCPU	Operator pods: 1.5–3 GB RAM Catalog pods: 0.2–0.4 GB RAM Operand: 10–27 GB RAM	Persistent storage: 400–713 GB Ephemeral storage: 5–12 GB Image storage: Up to 2.53 GB	The number of resources depends on whether IBM Knowledge Catalog is already installed in this instance of IBM Software Hub: If IBM Knowledge Catalog is installed, you need fewer resources to install IBM Manta Data Lineage. If IBM Knowledge Catalog is not installed, you need more resources to install IBM Manta Data Lineage. Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload.

vCPU

Memory

Storage

Notes

Operator pods:
0.75–1.5 vCPU

Catalog pods:
0.05–0.1 vCPU

Operand:
12–24 vCPU

Operator pods:
1.5–3 GB RAM

Catalog pods:
0.2–0.4 GB RAM

Operand:
10–27 GB RAM

Persistent storage:
400–713 GB

Ephemeral storage:
5–12 GB

Image storage:
Up to 2.53 GB

The number of resources depends on whether IBM Knowledge Catalog is already installed in this instance of IBM Software Hub:

If IBM Knowledge Catalog is installed, you need fewer resources to install IBM Manta Data Lineage.
If IBM Knowledge Catalog is not installed, you need more resources to install IBM Manta Data Lineage.

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

IBM Match 360

vCPU Memory Storage Notes

vCPU	Memory	Storage	Notes
Operator pods: 2 vCPU Catalog pods: 1 vCPU Operand: 27 vCPU	Operator pods: 2 GB RAM Catalog pods: 2 GB RAM Operand: 112 GB RAM	Persistent storage: 250 GB Ephemeral storage: 21 GB Image storage: Up to 18.95 GB	Minimum resources for an installation with a single replica per service. Persistent storage The raw size of shared storage depends on the storage class you use. For example, if you use `portworx-shared-gp3`, which has 3 replicas, multiply the storage by the number of replicas. For optimal operation, you should have at least 25% free space on all disks. Work with IBM Sales to get a more accurate sizing based on your expected workload.

Operator pods:
2 vCPU

Catalog pods:
1 vCPU

Operand:
27 vCPU

Operator pods:
2 GB RAM

Catalog pods:
2 GB RAM

Operand:
112 GB RAM

Persistent storage:
250 GB

Ephemeral storage:
21 GB

Image storage:
Up to 18.95 GB

Minimum resources for an installation with a single replica per service.

Persistent storage: The raw size of shared storage depends on the storage class you use. For example, if you use portworx-shared-gp3, which has 3 replicas, multiply the storage by the number of replicas.
For optimal operation, you should have at least 25% free space on all disks.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

IBM StreamSets

vCPU	Memory	Storage	Notes
Operator pods: 0.105 vCPU Catalog pods: 0.01 vCPU Operand: 44 vCPU	Operator pods: 0.75 GB RAM Catalog pods: 0.055 GB RAM Operand: 106 GB RAM	Persistent storage: 540 GB Ephemeral storage: 107.5 GB Image storage: Up to 24.73 GB	Minimum resources for an installation with 2 replicas per service.

Informix

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Catalog pods: 0.1 vCPU Operand: 2 vCPU	Operator pods: 0.256 GB RAM Catalog pods: 0.05 GB RAM Operand: 2 GB RAM	Persistent storage: 20 GB Ephemeral storage: 900 MB (default) Image storage: Up to 5.72 GB	Minimum resources for an installation with a single replica per service.

MANTA Automated Data Lineage

vCPU	Memory	Storage	Notes
Operator pods: 0.5 vCPU Catalog pods: 0.01 vCPU Operand: 13 vCPU	Operator pods: 0.5 GB RAM Catalog pods: 0.05 GB RAM Operand: 23 GB RAM	Persistent storage: 37 GB Ephemeral storage: 5 GB Image storage: Up to 5.41 GB	Minimum resources for an installation with a single replica per service. Work with IBM Sales to get a more accurate sizing based on your expected workload.

vCPU

Memory

Storage

Notes

Operator pods:
0.5 vCPU

Catalog pods:
0.01 vCPU

Operand:
13 vCPU

Operator pods:
0.5 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
23 GB RAM

Persistent storage:
37 GB

Ephemeral storage:
5 GB

Image storage:
Up to 5.41 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

MongoDB

vCPU	Memory	Storage	Notes
Operator pods: IBM: 0.1 vCPU Third-party: 0.5 vCPU Catalog pods: 0.01 vCPU Operand: User-defined	Operator pods: IBM: 0.256 GB RAM Third-party: 0.2 GB RAM Catalog pods: 0.05 GB RAM Operand: User-defined	Persistent storage: 100 GB Ephemeral storage: 0.256 GB Image storage: Up to 8.46 GB	Minimum resources for an installation with a single replica per service. Dedicated nodes are recommended. For details, see Setting up dedicated nodes. Development deployment 3 nodes Production deployment 3 nodes Recommended configuration Refer to the Ops Manager System Requirements to determine the appropriate specifications based on your expected workloads. Work with IBM Sales to get a more accurate sizing based on your expected workload.

vCPU

Memory

Storage

Notes

Operator pods:
IBM: 0.1 vCPU
Third-party: 0.5 vCPU

Catalog pods:
0.01 vCPU

Operand:
User-defined

Operator pods:
IBM: 0.256 GB RAM
Third-party: 0.2 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
User-defined

Persistent storage:
100 GB

Ephemeral storage:
0.256 GB

Image storage:
Up to 8.46 GB

Minimum resources for an installation with a single replica per service.

Dedicated nodes are recommended. For details, see Setting up dedicated nodes.

Development deployment: 3 nodes
Production deployment: 3 nodes
Recommended configuration: Refer to the Ops Manager System Requirements to determine the appropriate specifications based on your expected workloads.
Work with IBM Sales to get a more accurate sizing based on your expected workload.

OpenPages

vCPU	Memory	Storage	Notes
Operator pods: 0.5 vCPU Catalog pods: 0.01 vCPU Operand: 6 vCPU	Operator pods: 2 GB RAM Catalog pods: 0.05 GB RAM Operand: 20 GB RAM	Persistent storage: 252 GB Ephemeral storage: 10.9 GB Image storage: Up to 8.52 GB	When you provision the OpenPages service, you specify the size of the instance and the storage class to use. You also specify whether to use the database that is provided with the OpenPages service or a database that is on an external server. These values represent the minimum resources for OpenPages with a Db2 database on IBM Software Hub. Using a Db2 database on IBM Software Hub OpenPages uses Db2 as a service, which is different from the Db2 service in the services catalog. You can optionally provision the Db2 database on dedicated nodes. For details, see Provisioning an instance of OpenPages. Using a Db2 database outside of IBM Software Hub If you use a database outside of IBM Software Hub, the minimum requirements for vCPUs and memory are lower.

vCPU

Memory

Storage

Notes

Operator pods:
0.5 vCPU

Catalog pods:
0.01 vCPU

Operand:
6 vCPU

Operator pods:
2 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
20 GB RAM

Persistent storage:
252 GB

Ephemeral storage:
10.9 GB

Image storage:
Up to 8.52 GB

When you provision the OpenPages service, you specify the size of the instance and the storage class to use. You also specify whether to use the database that is provided with the OpenPages service or a database that is on an external server.

These values represent the minimum resources for OpenPages with a Db2 database on IBM Software Hub.

Using a Db2 database on IBM Software Hub

OpenPages uses Db2 as a service, which is different from the Db2 service in the services catalog.

You can optionally provision the Db2 database on dedicated nodes. For details, see Provisioning an instance of OpenPages.

Using a Db2 database outside of IBM Software Hub

If you use a database outside of IBM Software Hub, the minimum requirements for vCPUs and memory are lower.

Orchestration Pipelines

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
5 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
8 GB RAM

Persistent storage:
10 GB

Ephemeral storage:
9 GB

Image storage:
Up to 61.42 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

Planning Analytics

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
16 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
28 GB RAM

Persistent storage:
20 GB

Ephemeral storage: 50 GB (maximum)

Image storage:
Up to 29.61 GB

Work with IBM Sales to get a more accurate sizing based on your expected workload.

Select the size of your instance when you provision Planning Analytics. For details, see Provisioning the Planning Analytics service.

Product Master

vCPU

Memory

Storage

Notes

Operator pods:
0.3 vCPU

Catalog pods:
0.2 vCPU

Operand:
16 vCPU

Operator pods:
0.5 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
34 GB RAM

Persistent storage:
200 GB

Ephemeral storage:
22 GB

Image storage:
Up to 14.75 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

RStudio® Server Runtimes

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
1 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
8.8 GB RAM

Persistent storage:
Uses the persistent storage provisioned by the common core services.

Ephemeral storage:
Dictated by the runtimes. Approximately 1 GB for each runtime.

Image storage:
Up to 18.29 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

SPSS Modeler

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
0.25 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
1 GB RAM

Persistent storage:
Uses the persistent storage provisioned by the common core services.

Ephemeral storage:
3 GB (maximum)

Image storage:
Up to 10.57 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

Synthetic Data Generator

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
10.15 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
42.5 GB RAM

Persistent storage:
Uses the persistent storage provisioned by the common core services.

Ephemeral storage:
100 GB

Image storage:
Up to 6.66 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

Unstructured Data Integration

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
1 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
2.5 GB RAM

Persistent storage:
Not applicable

Ephemeral storage:
2.25 GB

Image storage:
Up to 8.8 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

Voice Gateway

vCPU

Memory

Storage

Notes

Operator pods:
0.2 vCPU

Catalog pods:
0.01 vCPU

Operand:
2 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
8 GB RAM

Persistent storage:
Not applicable

Ephemeral storage:
4 GB

Image storage:
3.39 GB

Minimum resources for a system that can provide voice-only support for up to 11 concurrent calls.

Dedicated nodes are recommended for production environments.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

Watson Discovery

vCPU

Memory

Storage

Notes

Operator pods:
0.05 vCPU

Catalog pods:
0.01 vCPU

Operand:
15 vCPU

Operator pods:
0.1 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
88–92 GB RAM

Persistent storage:

237 GB file storage
363 GB block storage
215 GB Multicloud Object Gateway storage

Ephemeral storage:
147 GB

Image storage:
Up to 77.80 GB

Starter deployments are sized for demonstration purposes only. Production deployments are sized for robust use. Be sure to choose the right size for your needs. You cannot change the deployment type after you install the service. If you need to change it later, you must reinstall. These values represent the minimum requirements for a Starter deployment.

CPUs must support the AVX2 instruction set.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

All of the Watson Discovery service instances associated with an instance of IBM Software Hub use the same pool of resources.

Watson Discovery supports only single-zone OpenShift deployments. You cannot install Watson Discovery on a multi-zone deployment.

Watson Machine Learning

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
6 vCPU

Operator pods:
0.5 GB RAM

Catalog pods:
0.5 GB RAM

Operand:
27 GB RAM

Persistent storage:
150 GB

Ephemeral storage:This information is not currently available.

Image storage:
Up to 93.10 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

AVX2 is recommended but not required for AutoAI experiments.

If you plan to use deep learning or models that require GPU, the service requires at least one GPU.

For more information about supported GPUs, see GPU requirements for models.

Watson OpenScale

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
13.25 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
71 GB RAM

Persistent storage:
100 GB

Ephemeral storage:
13.5 GB

Image storage:
Up to 36.64 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

Watson Speech services

vCPU

Memory

Storage

Notes

Operator pods:
0.3 vCPU

Catalog pods:
0.01 vCPU

Operand:
Speech to Text: 9 vCPU
Text to Speech: 6.5 vCPU

Operator pods:
0.3 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
Speech to Text: 33 GB RAM
Text to Speech: 16.4 GB RAM

Persistent storage:

900 GB
20 GB Multicloud Object Gateway storage

Ephemeral storage:
27 GB

Image storage:
Up to 88.08 GB

Minimum resources for an instance with a single replica per service using the default models and voices (US-English). The amount of vCPU, memory, and ephemeral storage that is required increases when you install additional models.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

CPUs must support the AVX2 instruction set.

All of the Watson Speech services service instances associated with an instance of IBM Software Hub use the same pool of resources.

Watson Studio

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
2 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
8.8 GB RAM

Persistent storage:
Uses the persistent storage provisioned by the common core services. Additional storage is required if you enable Visual Studio Code support.

Ephemeral storage:
5 - 10 GB

Image storage:
Up to 6.55 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

If Data Refinery is not installed, add the vCPU and memory required for Data Refinery to the information listed for Watson Studio.

If you enable the Visual Studio Code extension for Watson Studio, you must allocate a minimum of 500-600 MB of storage per user for installed extensions. For details, see To enable Visual Studio Code in Post-installation tasks for the Watson Studio service.

Watson Studio Runtimes

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
Dictated by the runtimes

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
Dictated by the runtimes

Persistent storage:
Uses the persistent storage provisioned by the common core services.

Ephemeral storage:
Dictated by the runtimes.

Image storage:
Up to 79.58 GB

Runtimes use on-demand vCPU and memory.

Watson Studio Runtimes includes the following runtimes:

Runtime 25.1 on Python 3.12
Runtime 24.1 on Python 3.11
Runtime 24.1 on Python 3.11 for GPU
Runtime 24.1 on R 4.3

The following runtimes have additional hardware requirements:

Runtime 24.1 on Python 3.11 for GPU: At least 1 GPU core is required to use this runtime.
For more information about supported GPUs, see GPU requirements for models.

watsonx.ai

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
27 vCPU

Operator pods:
1 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
665 GB RAM

Persistent storage:
Varies based on the foundation models that you plan to install. For more information, see Foundation models in watsonx.ai.

Ephemeral storage:
Varies based on the foundation models that you plan to install. For more information, see Foundation models in watsonx.ai.

Image storage:
Up to 8 TB with all models

Minimum resources for an installation with a single replica per service.

The same minimum resources are required for a watsonx.ai lightweight engine installation.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

This service requires GPUs. The number of GPUs depends on the models that you plan to run and whether you plan to run multiple models in parallel. For more information, see GPU requirements for models.

watsonx Assistant

vCPU

Memory

Storage

Notes

Operator pods:
1.5 vCPU

Catalog pods:
0.01 vCPU

Operand:
10 vCPU

Operator pods:
12.5 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
125 GB RAM

Persistent storage:

325 GB - 1340 GB
Only OpenShift Data Foundation and IBM Fusion Data Foundation require 1340 GB of storage. All other storage types require 325 GB.
100 GB Multicloud Object Gateway storage

Ephemeral storage:
30 - 135 GB

Image storage:
Up to 81.97 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

All of the watsonx Assistant service instances associated with an instance of IBM Software Hub use the same pool of resources.

Your hardware must meet the following additional requirements:

CPUs must have a clock speed of 2.4 GHz or higher
CPUs must support Linux® SSE 4.2
CPUs must support the AVX2 instruction set

If you plan to use conversational skills or conversational search features, the service requires GPUs. The number of GPUs depends on whether you plan to run multiple models in parallel.

For more information about supported GPUs, see GPU requirements for models.

watsonx™ BI

vCPU

Memory

Storage

Notes

Operator pods:
This information is not currently available.

Catalog pods:
This information is not currently available.

Operand:
This information is not currently available.

Persistent storage:
This information is not currently available.

Ephemeral storage:
This information is not currently available.

Image storage:
This information is not currently available.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

The service requires two GPUs.

For more information about supported GPUs, see GPU requirements for models.

watsonx Code Assistant™

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
7 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
25 GB RAM

Persistent storage:
70 GB

Ephemeral storage:
0.4 GB

Image storage:
60 GB with all models

Minimum resources for an installation with a single replica per service.

The service requires at least two GPUs.

For more information about supported GPUs, see GPU requirements for models.

watsonx Code Assistant for Red Hat Ansible® Lightspeed

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
6 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
11 GB RAM

Persistent storage:
63 GB

Ephemeral storage:
0.266 GB

Image storage:
57.64 GB

Minimum resources for an installation with a single replica per service.

The service requires at least one GPU. If you enable model customization after you install the service, the service requires two additional GPUs.

For more information about supported GPUs, see GPU requirements for models.

watsonx Code Assistant for Z

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
5 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
8 GB RAM

Persistent storage:
80 GB

Ephemeral storage:
0.135 GB

Image storage:
Up to 84.39 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

The service requires one GPU.

For more information about supported GPUs, see GPU requirements for models.

watsonx Code Assistant for Z Agentic

vCPU

Memory

Storage

Notes

Operator pods:
0.5 vCPU

Catalog pods:
0.01 vCPU

Operand:
1 vCPU

Operator pods:
1 GB RAM

Catalog pods:
0.5 GB RAM

Operand:
4 GB RAM

Persistent storage:
Not applicable

Ephemeral storage:
0.128 GB

Image storage:

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

The service requires one GPU. Alternatively, you can use an NVIDIA Multi-Instance GPU.

For more information about supported GPUs, see GPU requirements for models.

watsonx Code Assistant for Z Code Explanation

vCPU

Memory

Storage

Notes

Operator pods:
0.5 vCPU

Catalog pods:
0.1 vCPU

Operand:
2 vCPU

Operator pods:
1 GB RAM

Catalog pods:
0.5 GB RAM

Operand:
10 GB RAM

Persistent storage:
Not applicable

Ephemeral storage:
Not applicable

Image storage:
Up to 1.07 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

The service requires one GPU.

For more information about supported GPUs, see GPU requirements for models.

watsonx Code Assistant for Z Code Generation

vCPU

Memory

Storage

Notes

Operator pods:
0.5 vCPU

Catalog pods:
0.1 vCPU

Operand:
2 vCPU

Operator pods:
1 GB RAM

Catalog pods:
0.5 GB RAM

Operand:
4 GB RAM

Persistent storage:
Not applicable

Ephemeral storage:
1.08 GB

Image storage:

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

The service requires two GPUs.

For more information about supported GPUs, see GPU requirements for models.

watsonx.data

vCPU

Memory

Storage

Notes

Operator pods:
1 vCPU

Catalog pods:
0.01 vCPU

Operand:
22 vCPU

Operator pods:
0.75 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
70 GB RAM

Persistent storage:
542 GB

Ephemeral storage:
25 GB

Image storage:
Up to 24.19 GB

Minimum resources for an installation with a single replica of the Presto engine.

If you increase the number of Presto replicas, you need additional vCPU, memory, and ephemeral storage.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

If Analytics Engine powered by Apache Spark is not installed, add the vCPU and memory required for Analytics Engine powered by Apache Spark to the information listed for watsonx.data™.

If you want to use Milvus GPU indexes, the service requires at least one GPU.

For more information about supported GPUs, see GPU requirements for models.

watsonx.data Premium

vCPU

Memory

Storage

Notes

Operator pods:
25 vCPU

Catalog pods:
0.29 vCPU

Operand:
71 vCPU

Operator pods:
5.9 GB RAM

Catalog pods:
1.3 GB RAM

Operand:
316 GB RAM

Persistent storage:
2.89 TB

Ephemeral storage:
60 GB

Image storage:
Up to 33.62 GB

Minimum resources for an installation with a single replica of the Presto engine.

If you increase the number of Presto replicas, you need additional vCPU, memory, and ephemeral storage.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

The service requires at least 5 GPU.

For more information about supported GPUs, see GPU requirements for models.

watsonx.data intelligence

watsonx.data intelligence includes optional features. Review the sizing based on the features that you plan to enable.

Base service (required)

vCPU	Memory	Storage	Notes
Operator pods: 0.75 vCPU Catalog pods: 0.05 vCPU	Operator pods: 1.5 GB RAM Catalog pods: 0.2 GB RAM	Persistent storage: Not applicable Ephemeral storage: Not applicable Image storage: This information is not currently available.	Work with IBM Sales to get a more accurate sizing based on your expected workload.

Governance and catalogs (optional)

vCPU	Memory	Storage	Notes
Operator pods: 1.5 vCPU Catalog pods: 0.1 vCPU Operand: 36 vCPU	Operator pods: 3 GB RAM Catalog pods: 0.4 GB RAM Operand: 73 GB RAM	Persistent storage: 700 GB Ephemeral storage: 28 GB	Work with IBM Sales to get a more accurate sizing based on your expected workload.

Data quality (optional)

vCPU	Memory	Storage	Notes
Operand: 8 vCPU	Operand: 29 GB RAM	Persistent storage: Not applicable Ephemeral storage: 31 GB	This feature requires the Governance and catalogs feature.

Relationship explorer and semantic search (optional)

vCPU	Memory	Storage	Notes
Operator pods: 0.75 vCPU Catalog pods: 0.05 vCPU Operand: 6 vCPU	Operator pods: 1.5 GB RAM Catalog pods: 0.2 GB RAM Operand: 10 GB RAM	Persistent storage: 213 GB Ephemeral storage: 3 GB	This feature requires the Governance and catalogs feature.

Data lineage (optional)

vCPU	Memory	Storage	Notes
Operator pods: 0.75 vCPU Catalog pods: 0.05 vCPU Operand: 12 vCPU	Operator pods: 1.5 GB RAM Catalog pods: 0.2 GB RAM Operand: 10 GB RAM	Persistent storage: 400 GB Ephemeral storage: 5 GB	Work with IBM Sales to get a more accurate sizing based on your expected workload.

Data products (optional)

vCPU	Memory	Storage	Notes
Operator pods: 0.75 vCPU Catalog pods: 0.05 vCPU Operand: 2 vCPU	Operator pods: 1.5 GB RAM Catalog pods: 0.2 GB RAM Operand: 2 GB RAM	Persistent storage: Not applicable Ephemeral storage: 2 GB	Work with IBM Sales to get a more accurate sizing based on your expected workload.

Gen AI running on CPU (optional)

You can use CPU or GPU to run the foundation models for this feature.

vCPU	Memory	Storage	Notes
Operand: 11 vCPU	Operand: 14 GB RAM	Persistent storage: 10 GB Ephemeral storage: 3 GB	For better performance, use GPU.

Gen AI running on GPU (optional)

You can use CPU or GPU to run the foundation models for this feature. GPU offers better performance than CPU.

vCPU

Memory

Storage

Notes

Operand:
3 vCPU

Operand:
4 GB RAM

Persistent storage:
10 GB

Ephemeral storage:
3 GB

This option requires 3 GPU.

For more information about supported GPUs, see GPU requirements for models.

Semantic embedding (optional)

vCPU	Memory	Storage	Notes
Operand: 2 vCPU	Operand: 3 GB RAM	Persistent storage: Not applicable Ephemeral storage: 1 GB	This feature requires the Gen AI feature.

AI search (optional)

vCPU

Memory

Storage

Notes

Operand:
4 vCPU

Operand:
4 GB RAM

Persistent storage:
Not applicable

Ephemeral storage:
1 GB

This feature requires either of the following features:

Governance and catalogs
Data products

watsonx.governance

watsonx.governance™ includes optional features. Review the sizing based on the features that you plan to enable.

Base service (required)

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Persistent storage:
Not applicable

Ephemeral storage:
250 MB

Image storage:
47.58 GB

Minimum resources for an installation with a single replica per service.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

AI Factsheets (optional)

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Catalog pods: 0.01 vCPU Operand: 0.3 vCPU	Operator pods: 0.256 GB RAM Catalog pods: 0.05 GB RAM Operand: 1.2 GB RAM	Persistent storage: Uses the persistent storage provisioned by the common core services. Ephemeral storage: 300 GB	Work with IBM Sales to get a more accurate sizing based on your expected workload.

OpenPages (optional)

vCPU	Memory	Storage	Notes
Operator pods: 0.5 vCPU Catalog pods: 0.01 vCPU Operand: 6 vCPU	Operator pods: 2 GB RAM Catalog pods: 0.05 GB RAM Operand: 20 GB RAM	Persistent storage: 252 GB Ephemeral storage: 10.9 GB	Work with IBM Sales to get a more accurate sizing based on your expected workload.

Watson OpenScale (optional)

vCPU	Memory	Storage	Notes
Operator pods: 0.1 vCPU Catalog pods: 0.01 vCPU Operand: 13.25 vCPU	Operator pods: 0.256 GB RAM Catalog pods: 0.05 GB RAM Operand: 71 GB RAM	Persistent storage: 100 GB Ephemeral storage: 13.5 GB	Work with IBM Sales to get a more accurate sizing based on your expected workload.

watsonx Orchestrate

vCPU

Memory

Storage

Notes

Operator pods:
Up to 1 vCPU

Catalog pods:
0.01 vCPU

Operand:
68–110 vCPU

Operator pods:
Up to 7.4 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
425–444 GB RAM

Persistent storage:
Up to 1510 GB

Ephemeral storage:
91-125 GB

Image storage:
Up to 156 GB

Minimum resources for a highly available production deployment.

Work with IBM Sales to get a more accurate sizing based on your expected workload.

The service requires a minimum of 2 GPUs for non-HA deployments.

For more information about supported GPUs, see GPU requirements for models.

Automatically installed dependencies

Automatically installed dependencies provide underlying functionality for services. Use the following sections to understand the hardware requirements for:

Canvas
Common core services
Db2 as a service
Db2U

Use the following information to determine whether you have the minimum required resources to install each component on your cluster.

Canvas

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
0.15 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
.0.6 GB RAM

Persistent storage:
Uses the persistent storage provisioned by the common core services.

Ephemeral storage:
0.02 GB

Image storage:
Up to 1.53 GB

Automatically installed by services that require it.

Depending on the services that you install, this software is installed once in each Red Hat OpenShift project where IBM Software Hub is installed. For details, see Service software requirements.

Common core services

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
11 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
18.3 GB RAM

Persistent storage:
500 GB

Ephemeral storage:
100 GB

Image storage:
Up to 23.83 GB

Automatically installed by services that require it.

Depending on the services that you install, this software is installed once in each Red Hat OpenShift project where IBM Software Hub is installed. For details, see Service software requirements.

Db2 as a service

vCPU

Memory

Storage

Notes

Operator pods:
0.1 vCPU

Catalog pods:
0.01 vCPU

Operand:
0.3 vCPU

Operator pods:
0.256 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
0.8 GB RAM

Persistent storage:
Not applicable

Ephemeral storage:
0.5 GB

Image storage:
Up to 2.02 GB

Automatically installed by services that require it.

Depending on the services that you install, this software is installed once in each Red Hat OpenShift project where IBM Software Hub is installed. For details, see Service software requirements.

Db2U

vCPU

Memory

Storage

Notes

Operator pods:
0.6 vCPU

Catalog pods:
0.01 vCPU

Operand:
Not applicable.

Operator pods:
0.7 GB RAM

Catalog pods:
0.05 GB RAM

Operand:
Not applicable.

Persistent storage:
Not applicable

Ephemeral storage:
0.5 GB

Image storage:
Up to 40.27 GB

Automatically installed by services that require it.

Depending on the services that you install, the operands for this software might be installed multiple times in each Red Hat OpenShift project where IBM Software Hub is installed.

The operator is installed once per instance of IBM Software Hub.

The operands are generated by the services that have a dependency on Db2U.

For a list of services that have a dependency on Db2U, see Service software requirements.