Build Red Hat OpenShift on IBM Cloud cluster configurations with worker pools, encryption, and autoscaling.
Last verified: May 2026
Build ROKS cluster configurations with worker pools, VPC networking, OCP entitlements, encryption, and autoscaling.
Required Fields
nameopenshiftVersionproviderworkerPoolscosInstanceCrnOutput will appear here...The builder collects cluster name, ROKS version (a Kubernetes version with `_openshift` suffix), VPC, worker pool definitions, encryption config, and integrations. It validates the ROKS version against currently-supported releases and emits an `ibm_container_vpc_cluster` Terraform resource with `kube_version` set appropriately. Additional pools become `ibm_container_vpc_worker_pool` resources.
Red Hat OpenShift on IBM Cloud (ROKS) is a managed OpenShift offering with the same operational model as IKS but with the OpenShift control plane, OperatorHub, and OpenShift-specific networking. The ROKS Cluster Builder generates a complete cluster spec — worker pools, encryption, monitoring integration, and entitlement configuration — output as `ibm_container_vpc_cluster` with the `kube_version` set to a ROKS release identifier.
A team that was running OpenShift on bare metal — and dealing with all the operational cost — moves to ROKS to free up engineering time. They generate the ROKS cluster spec with the builder, apply, and a week later have migrated 90% of their applications. The remaining 10% needed minor adjustments (storage class changes, ingress controller config) that the team estimates would have taken three months of in-place OpenShift upgrades.
Operators are the OpenShift superpower — invest in learning the OperatorHub catalog. Instead of writing custom Kubernetes manifests for things like databases or monitoring, you install an operator that manages the lifecycle. This is the operational difference from vanilla Kubernetes.
Use OpenShift's built-in image registry instead of standing up a separate one. It's already integrated with the cluster's auth and serves as the default for the OpenShift build pipeline.
Yes — ROKS clusters include the OpenShift platform entitlement at no extra OpenShift license cost (you pay for the worker infrastructure and IBM Cloud services). This is one of the main value props vs running OpenShift on raw IaaS where you'd be paying both the infrastructure and the Red Hat subscription separately.
Both are managed OpenShift on a public cloud. ROKS integrates with IBM Cloud-native services (Cloud Object Storage, IBM Key Protect, IBM Cloud Monitoring); ROSA integrates with AWS-native services. Pick based on where the rest of your stack lives. The OpenShift experience itself — Operators, console, developer tooling — is consistent.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.