> For the complete documentation index, see [llms.txt](https://run-ai-docs.nvidia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://run-ai-docs.nvidia.com/self-hosted/2.21/getting-started/installation/support-matrix.md).

# Support Matrix

The support matrix outlines the verified compatibility standards for NVIDIA Run:ai v2.21. To ensure a stable and performant deployment, all infrastructure components, including Kubernetes/OpenShift distributions, NVIDIA Operators, and specialized frameworks, must align with the versions specified below. Use this matrix as a validation checklist prior to performing new installations or upgrades.

## Operator and Framework Versions

| Component                                                                                                                                                                                 | Supported Versions    |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- |
| [NVIDIA GPU Operator](https://run-ai-docs.nvidia.com/self-hosted/2.21/getting-started/installation/install-using-helm/system-requirements.md#nvidia-gpu-operator)                         | 24.9-25.3             |
| [NVIDIA Network Operator](https://run-ai-docs.nvidia.com/self-hosted/2.21/getting-started/installation/install-using-helm/system-requirements.md#nvidia-network-operator)                 | 24.4-25.10            |
| [NVIDIA DRA driver](https://run-ai-docs.nvidia.com/self-hosted/2.21/getting-started/installation/install-using-helm/system-requirements.md#nvidia-dynamic-resource-allocation-dra-driver) | 25.3-25.8             |
| [Prometheus / Kube‑Prometheus Stack](https://run-ai-docs.nvidia.com/self-hosted/2.21/getting-started/installation/install-using-helm/system-requirements.md#prometheus)                   | 2.53 / 61.0 and above |
| [Kubeflow Training Operator](https://run-ai-docs.nvidia.com/self-hosted/2.21/getting-started/installation/install-using-helm/system-requirements.md#distributed-training)                 | 1.9.2                 |
| [MPI Operator](https://run-ai-docs.nvidia.com/self-hosted/2.21/getting-started/installation/install-using-helm/system-requirements.md#distributed-training)                               | 0.6.0 or later        |
| [Knative Serving](https://run-ai-docs.nvidia.com/self-hosted/2.21/getting-started/installation/install-using-helm/system-requirements.md#inference)                                       | 1.11 – 1.16           |

## Supported NVIDIA GPUs

NVIDIA Run:ai v2.21 is compatible with all Data Center GPUs supported by the NVIDIA GPU Operator. Hardware compatibility is determined by the specific version of the GPU Operator deployed within your cluster.

* Supported operator range - NVIDIA Run:ai v2.21 supports GPU Operator versions 24.9 through 25.3.
* Hardware verification - To confirm if a specific GPU model is supported, please cross-reference your Operator version with the [Supported NVIDIA Data Center GPUs and Systems](https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/platform-support.html#supported-nvidia-data-center-gpus-and-systems) documentation.

{% hint style="info" %}
**Note**

* NVIDIA DGX Spark and NVIDIA Jetson are not supported.
* In addition to GPU Operator compatibility, support also depends on the framework being used (for example, CUDA, PyTorch, TensorFlow, or NVIDIA NIM). Before running a workload, verify that the selected framework version supports your target GPU architecture according to the relevant support matrix.
  {% endhint %}

## Orchestration Platform Compatibility

NVIDIA Run:ai v2.21 supports a wide range of Kubernetes distributions across on-premises, hybrid, and public cloud environments. Use the table below to verify version requirements for your specific platform.

| Orchestration Platform                 | Versions                         | Engine     | x86       | ARM           |
| -------------------------------------- | -------------------------------- | ---------- | --------- | ------------- |
| Upstream Kubernetes                    | 1.30-1.32                        | Containerd | Supported | Supported     |
| Red Hat OpenShift                      | 4.14-4.18                        | CRI-O      | Supported | Not supported |
| Amazon Elastic Kubernetes Engine (EKS) | Based on the upstream Kubernetes | Containerd | Supported | Supported     |
| Google Kubernetes Engine (GKE)         | Based on the upstream Kubernetes | Containerd | Supported | Supported     |
| Azure Kubernetes Service (AKS)         | Based on the upstream Kubernetes | Containerd | Supported | Supported     |
| Oracle Kubernetes Engine (OKE)         | Based on the upstream Kubernetes | Containerd | Supported | Supported     |
| Rancher Kubernetes Engine 2 (RKE2)     | Based on the upstream Kubernetes | Containerd | Supported | Supported     |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://run-ai-docs.nvidia.com/self-hosted/2.21/getting-started/installation/support-matrix.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
