Chapter 1. Openshift Container Platform cluster prerequisites


Before deploying Distributed Inference with llm-d on Openshift Container Platform, verify that your cluster meets minimum requirements for platform version, GPU availability, operator dependencies, and client tool versions.

Your Openshift Container Platform cluster must meet the following requirements:

Expand
Table 1.1. Openshift Container Platform cluster requirements
RequirementDetails

Openshift Container Platform version

4.19 or later

API server access

Access to the cluster through the OpenShift CLI (oc) or kubectl

RBAC permissions

Ability to create namespaces, install operators, and deploy workloads, typically cluster-admin or equivalent permissions

GPU node pool

At least one machine set or node pool with GPU worker nodes provisioned

Network connectivity

Outbound internet access to pull images from registry.redhat.io, OCI-packaged Helm charts from registry.redhat.io/rhai/rhai-on-openshift-chart:v3.4, and upstream container registries

OpenShift Service Mesh

OpenShift Service Mesh v2 must not be installed in the cluster. The Helm chart installs the Istio Sail Operator, which conflicts with Service Mesh v2.

Expand
Table 1.2. Operator dependencies
OperatorDetails

LeaderWorkerSet Operator

Installed automatically by the Helm chart through OLM. No manual installation is required. For more information, see the LeaderWorkerSet Operator documentation.

NVIDIA GPU Operator

Must be installed and configured to manage GPU nodes. For more information, see AI accelerator prerequisites for Openshift Container Platform.

Expand
Table 1.3. Gateway requirements
RequirementDetails

GatewayClass and Gateway

The Helm chart automatically creates a GatewayClass and Gateway named openshift-ai-inference in the openshift-ingress namespace. For more information about Gateway API, see Gateway API with Openshift Container Platform Networking.

LoadBalancer

If the cluster does not include support for LoadBalancer services, configure load balancing with MetalLB

Important

The default Helm-created Gateway uses allowedRoutes.namespaces.from: All, which permits any namespace in the cluster to attach routes to the inference gateway. For production deployments, create a Gateway with restricted namespace access to prevent untrusted services from hijacking inference traffic. For more information, see Configure the inference gateway on Openshift Container Platform.

Expand
Table 1.4. Bandwidth and storage requirements
RequirementDetails

Network bandwidth for initial deployment

OCI-packaged Helm charts from registry.redhat.io/rhai/rhai-on-openshift-chart:v3.4 and 2-3 GB of container images

Network bandwidth for model weights

Model weights must be downloaded from the model registry. Size depends on the model. Plan for sustained bandwidth during inference based on request rate and model size.

Node storage

50 GB per GPU node for container images and ephemeral storage. Cache local copies of frequently accessed model weights for faster startup.

Expand
Table 1.5. Client tool requirements
ToolVersion

OpenShift CLI (oc)

4.19 or later

Helm

3.17 or later with OCI support

Podman or Docker

Latest stable release for local image verification

Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top