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:
| Requirement | Details |
|---|---|
| Openshift Container Platform version | 4.19 or later |
| API server access |
Access to the cluster through the OpenShift CLI ( |
| RBAC permissions |
Ability to create namespaces, install operators, and deploy workloads, typically |
| 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 |
| 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. |
| Operator | Details |
|---|---|
| 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. |
| Requirement | Details |
|---|---|
| GatewayClass and Gateway |
The Helm chart automatically creates a |
| LoadBalancer |
If the cluster does not include support for |
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.
| Requirement | Details |
|---|---|
| Network bandwidth for initial deployment |
OCI-packaged Helm charts from |
| 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. |
| Tool | Version |
|---|---|
|
OpenShift CLI ( | 4.19 or later |
| Helm | 3.17 or later with OCI support |
| Podman or Docker | Latest stable release for local image verification |