Technology1 min read

A day in the life of an NVIDIA H100 on Red Hat OpenShift 5

By · Published by Everything Blog

In short

Historically, Kubernetes managed accelerators as basic numbers, forcing workloads to claim entire physical cards regardless of actual compute requirements. Red Hat OpenShift 5 solves this by using dynamic resource allocation to inspect detailed device profiles and match incoming jobs via explicit ResourceClaims. Under this architecture, an NVIDIA H100 80 GB GPU can expose both whole-device access and fractional slices without triggering hardware conflicts. Meanwhile, a dedicated DeviceClass maintains backward compatibility by automatically converting legacy integer requests into modern claims without requiring manifest rewrites.

Key points

  • Workload scheduling now relies on precise hardware profiles described directly within dyn…: Workload scheduling now relies on precise hardware profiles described directly within dynamic ResourceClaims.
  • Shared counter sets prevent the scheduler from creating conflicting allocations between f…: Shared counter sets prevent the scheduler from creating conflicting allocations between full GPUs and smaller sliced instances.
  • Automatic conversion by the DeviceClass ensures existing application manifests function p…: Automatic conversion by the DeviceClass ensures existing application manifests function properly without needing manual rewrites.

Sources checked by our analysis pipeline: 1

For years, asking Kubernetes for a GPU has meant writing 1 line: nvidia.com/gpu: 1

. The value requested in that line is an integer. The scheduler knows how many GPUs a node has and how many a pod wants, and nothing else. It can't tell which GPU you get, how much of its memory you need, whether a slice of it would do, or whether the card had a fault 10 minutes ago. You get the whole card or nothing.

Dynamic resource allocation (DRA) changes the model. A DRA driver publishes every device as an API object with attributes and capacity. Workloads describe what they need in a ResourceClaim. The scheduler, not a node-local plugin, matches them. Red Hat OpenShift 5, built on Kubernetes 1.36, ships 6 DRA features on top of that model. The clearest way to show what they do is to watch them work together on a single card.

Red Hat OpenShift lets teams manage AI workloads through familiar Kubernetes APIs and operational workflows. DRA adds richer ways to request and allocate accelerators, helping platform teams match…

Technology