System requirements
Ready to install Cloud Solution Workbench? Before you get started, use the information in this document to determine whether you have sufficient resources to install the service and the required software dependencies for the service.
Hardware resources
The hardware requirements for Cloud Solution Workbench vary significantly based on the specific features you are utilizing.
Minimum hardware resources for Installation
The following table provides an overview of the minimum requirements for a typical installation including the Cloud Solution Workbench Product installation and the required third-party components.
| Hardware | CPU | Memory |
|---|---|---|
| x86-64 | 12 cores | 64 GB |
We recommend using a minimum of 3 worker nodes to facilitate pod scheduling effectively.
Minimum hardware resources for Runtime
Runtime hardware is required only if you use Managed Stacks to deploy generated services. See Install runtime for Managed Stacks.
Storage
A dynamic storage provisioner is required to be present on the cluster. The core product has only modest requirements in terms of PVC storage access modes - only ReadWriteOnce (RWO) is required. If you are installing other pre-requirements software onto the same cluster, i.e. MongoDB, kafka, Keycloak, additional access modes might be required.
Use a storage provider with 500 GB or more of available space for your cluster. Tested providers include AWS EBS volumes, NFS, Portworx and OpenShift Container Storage. Squash must not be enabled on the NFS server, and all nodes in the cluster must have access to mount the NFS server and read/write access.
Container platform
Cloud Solution Workbench can be installed on OpenShift or Kubernetes.
Kubernetes setup
Please make sure you are running one of the following versions:
- Kubernetes (version 1.33)
OpenShift setup
Please make sure you are running one of the following versions:
To set up OpenShift please follow the instructions in the OpenShift documentation.
For some preparatory steps a user with the cluster admin role is required. These steps are clearly marked. Once the product is installed this role is no longer required for the users working with Cloud Solution Workbench.
We strongly recommend hardening the Red Hat Enterprise Linux CoreOS (RHCOS). This prevents attackers from gaining access to the data of an OpenShift container. See also:
Required third-party components
The Cloud Solution Workbench requires the following third-party components with the specified versions. These can be either deployed into the cluster or be deployed separately.
Required dependencies for Red Hat OpenShift installation
| Component | Required version | Minimum specifications for worker nodes | Minimum storage requirements | Optional |
|---|---|---|---|---|
| Red Hat build of Keycloak Operator | Version 26.6 | yes, one identity provider is required (Keycloak or Entra ID) | ||
| Microsoft Entra ID | yes, one identity provider is required (Keycloak or Entra ID); see Helm values | |||
| Redis Enterprise Operator | Version 8.2 | yes |
The remaining OpenShift components (Kafka, Apicurio Registry, GitOps, Pipelines, Logging Operator, MongoDB for deployed services) are needed only for Managed Stacks. See Install runtime for Managed Stacks.
Required dependencies for Kubernetes installation
| Component | Required version | Minimum specifications for worker nodes | Minimum storage requirements | Optional |
|---|---|---|---|---|
| Keycloak | Version 26.6 | yes, one identity provider is required (Keycloak or Entra ID) | ||
| Microsoft Entra ID | yes, one identity provider is required (Keycloak or Entra ID); see Helm values |
The remaining Kubernetes components (Kafka, Apicurio Registry, ArgoCD, Tekton, MongoDB for deployed services) are needed only for Managed Stacks. See Install runtime for Managed Stacks.
Keycloak is only supported with HTTPS mode enabled. It needs proper certificate and hostname setup.
Supported Git providers
Currently, the following Git providers are supported:
- GitLab self-managed
- Azure DevOps
- Bitbucket Server
- GitHub Enterprise
- GitHub Public
- Gitea
Of course it is not needed to create a new git provider instance, you can use your existing one. Also, it is not needed that the used git providers run inside the OpenShift cluster, but they can.