Supported Platforms and Software Components | NVIDIA Confidential Computing

Following are the platforms supported by the NVIDIA Confidential Containers Reference Architecture.

This page is relevant to the following users:

The Hardware IT Administrator uses the hardware tables to confirm that the selected CPU and GPU are validated for Confidential Computing before configuring the system.
The Host OS Administrator uses the hardware tables to confirm validated host OS and kernel versions.
The Kubernetes Cluster Administrator uses the component matrix to confirm supported versions.

Hardware

NVIDIA GPUs

GPU	Passthrough
NVIDIA H100	Single-GPU
NVIDIA H200	Single-GPU
NVIDIA H100 Protected PCIe (PPCIe)	Multi-GPU
NVIDIA H200 Protected PCIe (PPCIe)	Multi-GPU
NVIDIA B200	Single-GPU, Multi-GPU
NVIDIA HGX B300	Single-GPU, Multi-GPU
NVIDIA RTX Pro 6000 BSE	Single-GPU

Multi-GPU passthrough on NVIDIA Hopper HGX systems requires that you set the Confidential Computing mode to ppcie mode. Refer to Managing the Confidential Computing Mode for details.

For both single and multi GPU Passthrough, all GPUs on the host must be configured for Confidential Computing and all GPUs must be assigned to one Confidential Container virtual machine. Configuring only some GPUs on a node for Confidential Computing is not supported.

Host Platforms

CPU Platform	TEE	Host Operating System	Host Kernel Version
AMD Genoa / Milan	AMD SEV-SNP	Ubuntu 25.10 or 26.04	6.17+
Intel Emerald Rapids (ER) / Granite Rapids (GR)	Intel TDX	Ubuntu 25.10 or 26.04	6.17+

For additional information on node configuration, refer to the Confidential Computing Deployment Guide for information about supported NVIDIA GPUs, such as the NVIDIA Hopper H100.

The following topics in the deployment guide apply to a cloud-native environment:

Hardware selection and initial hardware configuration, such as BIOS settings.
Host operating system selection, initial configuration, and validation.

When following the cloud-native sections in the deployment guide linked above, use Ubuntu 25.10 or 26.04 as the host OS with its default kernel version and configuration.

For additional resources on machine setup:

Refer to the NVIDIA Trusted Computing Solutions website.
Refer to the Licensing page for more information on the licensing requirements for NVIDIA Confidential Computing capabilities.

Supported Software Components

Cluster and Deployment Software

The installation guides begin with an existing Kubernetes cluster that uses containerd. You then install Kata Containers and the NVIDIA GPU Operator.

Component	Release/Version	Installation
Kubernetes	1.32 +	Prerequisite, must already be installed on the cluster hosts.
containerd	2.3.x	Prerequisite, must already be installed on the cluster hosts.
Kata Containers	4.0.0	Installed with the `kata-deploy` Helm chart by following the Quickstart Install or Detailed Install Guide.
NVIDIA GPU Operator and its components.Refer to the GPU Operator Component Matrix for the list of components and versions included in each release.	v26.3.1 and higher	Installed by following the Quickstart Install or Detailed Install Guide.

Kata-provided Guest and Runtime Artifacts

The supported kata-deploy Helm chart installs the guest OS, guest kernel, OVMF, and QEMU artifacts listed in the following table as part of Kata Containers. You do not supply or install these artifacts individually.

Artifact	Release/Version
Guest OS	Distroless, with NVRC v0.1.5, NVIDIA GPU driver 595.58.03, and guest-components v0.21.0 artifacts.
Guest kernel	6.18.35
OVMF	edk2-stable202511
QEMU	11.0.1 + Patches

Separately Deployed Components and Interfaces

The following components and interfaces are not installed by the Quickstart Install or Detailed Install Guide.

Interface or Component	Version	When It Is Needed	How It Is Provided
Trustee	v0.21.0	Required for attestation and secret or key release. This architecture validates Trustee v0.21.0 with guest-components v0.21.0 in the Kata guest.	The Attestation quickstart installs a local evaluation Trustee v0.21.0. Deploy a production Trustee separately by following the upstream Confidential Containers documentation.
Kata Lifecycle Manager	0.1.8	Optional for Kata Containers upgrades and day-two lifecycle management.	Install separately by following the upstream Kata Lifecycle Manager documentation.
Kata Containers genpolicy	4.1.0	Used to generate an agent security policy for attested production workloads. Refer to Attach a Kata Agent Security Policy.	Download `genpolicy` 4.1.0 from the Kata Containers 4.1.0 release.

Users may leverage Red Hat OpenShift Sandboxed Containers to deploy Confidential Containers.