Compute resources for development environments

Resource requirements for operators and deployed instances of IBM Cloud Pak® for Integration in development environments.

Tip: Because this is a minimum configuration, your system requirements will change based on actual usage. For more information on the requirements for high availability deployments, see Resource requirements for high availability.

Resource requirements for Cloud Pak for Integration

This table indicates the minimum required values for installation of Cloud Pak for Integration in various environments.

Use case Nodes Cores per node Memory request (GiB)
Minimal proof of concept environment without failover 1 24 24
Small production environment with multiple workers for failover 3 8 24
Large production environment with multiple components installed 3 32 64

Notes:

  • A small production environment provides failover but limited space for workload.

  • A large production environment provides both failover and ample space for workload.

Resource requirements for operators

Cloud Pak for Integration operators must be installed before their associated instances can be deployed. This table lists the minimum resources for operators that should be factored in when sizing an OpenShift cluster:

Operator CPU request (cores) CPU limit (cores) Memory request (GiB) Memory limit (GiB) Disk space (GB)
IBM Cloud Pak for Integration 0.2 0.2 1 1 None
IBM Automation Foundation assets 0.25 0.25 0.5 0.5 None
IBM API Connect 0.075 1 0.125 1 None
IBM MQ 1 1 1 1 None
IBM Event Streams 0.2 1 1 1 None
IBM Event Endpoint Management 0.2 1 0.25 0.5 None
IBM Event Processing 0.2 1 0.25 0.5 None
IBM Operator for Apache Flink 0.2 1 0.25 0.5 None
IBM App Connect 0.1 none 0.125 1 None
IBM DataPower Gateway 0.75 2.25 1 2.5 None
IBM Aspera HSTS 0.2 0.5 0.2 0.5 None
IBM Cloud Pak foundational services 1.5 3.4 1.6 3.5 None

CPU (cores) and Memory values represent the total amount of CPU and memory required for the OpenShift cluster as a whole, not the required amount per node.

Resource requirements for instances

This table lists the resource requirements for instances.

Note: Some deployment environments may have restrictions on resource usage, which could require you to have more worker nodes in order to deploy a particular instance. For example, public cloud providers have limits on number of persistent volumes for public cloud providers. that may affect OpenShift cluster sizing requirements.
Instance type CPU request (cores) CPU limit (cores) Memory request (GiB) Memory limit (GiB) Disk space (GB)
Platform UI 1.0 1.0 1.0 1.0 N/A
Automation assets 0.7 0.7 1.0 1.0 0.4
Messaging server 0.1 0.1 1.0 1.0 2
API Connect cluster 4.3 28 20 67 280
Event Manager 0.25 0.5 0.25 0.5 0.5
Event Gateway 0.5 1.0 0.5 1.0 N/A
Event Processing 1.0 2.0 1.0 2.0 0.5
Queue manager 0.5 0.5 1 1 2
Kafka cluster 2.8 12.2 6 14 2
Integration dashboard 0.1 0.75 0.2 1 2.3
Integration design 1.6 7.2 2.9 7.4 10
Integration runtime 0.5 0.5 0.5 0.5 N/A
Enterprise gateway 1 1 4 4 N/A
High-speed transfer server 5.2 52 5 30 120
IBM Cloud Pak foundational services 1.2 1.2 1.5 1.5 2

CPU (cores) and Memory values represent the total amount of CPU and memory required for the OpenShift cluster as whole, not the required amount per node.