{"resourceId":"nvidia-gpu-operator-26-7-0-dra-constraints-2026","versions":[{"version":"external-05001af4557e8c4147b1b14c234207d47281aad3264d5285ac85b00b80923caf","resource":{"id":"nvidia-gpu-operator-26-7-0-dra-constraints-2026","title":"GPU Operator 26.7.0: GPUCluster DRA management and passthrough allocation pitfalls","organization":"NVIDIA","sector":"Kubernetes GPU platform software","geography":"Global (product documentation)","publishedAt":"2026 (v26.7.0 release notes)","publicationDate":null,"eventDate":null,"sourceName":"NVIDIA GPU Operator Documentation","sourceLabel":"Vendor standards / release notes","sourceUrl":"https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/release-notes.html","evidenceClass":"standards-guidance","outcomeClass":"cautionary","topics":["infrastructure","developers-agents","data-security"],"finding":"GPU Operator 26.7.0 adds GPUCluster CR to manage DRA Driver for GPUs (full GPU and preconfigured MIG via ResourceClaims), KubeVirt VFIO passthrough with DRA, driver 595.91.07 stack updates, and in-place patch restarts. Requires Kubernetes v1.34.2+, driver 580+, CDI runtime; cannot mix GPUCluster with ClusterPolicy. Known issue: concurrent container and VFIO claims on the same physical GPU can race—submit serially or dedicate nodes.","sledRelevance":"Critical platform constraint for SLED clusters adopting Dynamo shadow recovery or NIM DRA allocation—both need modern K8s DRA. Mixing VM passthrough and containers without node dedication is a concrete failure mode.","evidence":"Opened latest release notes for 26.7.0 New Features and Known Issues describing GPUCluster, K8s v1.34.2+ requirement, mutual exclusion with ClusterPolicy, and DRA passthrough double-allocation race.","architectureImplications":"Choose GPUCluster or ClusterPolicy—not both; align K8s minor version before promising DRA features used by Dynamo/NIM.","governanceImplications":"Platform upgrade boards must approve 1.34.2+ moves in regulated clusters.","securityPrivacyImplications":"VFIO passthrough + containers on one node needs clear tenancy isolation policy.","caveats":"Release notes are version living docs; some DRA capabilities remain alpha/disabled by default.","streamIds":["nvidia"],"roles":{"sales":"Tie GPU Operator upgrades to Kubernetes version commitments when selling DRA-dependent inference features.","engineering":"Migrate carefully to GPUCluster; enforce serial claim preparation or node pools separating VFIO and containers.","delivery":"Include ClusterPolicy-to-GPUCluster migration and race-condition runbooks in delivery."},"roleDetails":{"sales":{"customerProblem":"Buyers want DRA-based GPU sharing and VM+container flexibility without knowing version floors.","stakeholders":["platform eng","virtualization team","security"],"discoveryQuestions":["Kubernetes version today?","Using ClusterPolicy or planning GPUCluster?","Do VMs and containers share GPU nodes?"],"valueHypothesis":"GPUCluster DRA unlocks modern allocation when version prerequisites are met.","potentialEngagement":"Platform readiness review for 26.7.0 DRA features.","unsupportedClaims":["Works on any K8s 1.28 cluster","Safe simultaneous container+VFIO claims on one GPU"]},"engineering":{"fit":"Fit for clusters 1.34.2+ adopting DRA; migration required from ClusterPolicy.","architectureIntegration":"GPUCluster manages DRA driver, DCGM, validation workload; ResourceClaims select GPUs/MIG.","prerequisites":["K8s 1.34.2+","driver 580+","CDI runtime"],"constraints":["No ClusterPolicy coexistence","Passthrough race known issue","Some DRA alpha"],"security":"Separate node pools for VFIO vs containers when isolation required.","proofOfValue":["ResourceClaim binds","No dual-prepare failures","DCGM metrics present"]},"delivery":{"work":"Upgrade Operator, cut over to GPUCluster, validate claims, document node roles.","dependencies":["K8s upgrade","workload owners","KubeVirt team if VMs"],"ownership":"GPU platform team.","skillsAdoption":"DRA ResourceClaim literacy for app teams.","governanceCheckpoints":["Upgrade CAB","Coexistence ban confirmation","Known-issue communication"],"acceptanceCriteria":["GPUCluster Ready","Test claims for MIG and full GPU","Written node dedication policy if VFIO used"],"risks":["Partial migration leaving ClusterPolicy","Silent claim races"]}},"retrievedAt":"2026-09-17T03:14:00Z","enrichedAt":"2026-09-17T03:20:00Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Stable GPU scheduling improves shared research access reliability.","procurementImplications":"Require supported K8s versions in managed Kubernetes contracts when DRA features are in scope.","operatingModelImplications":"Platform must own DRA lifecycle separately from app teams.","sourceVerification":{"openedUrl":"https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/release-notes.html","referenceExcerpt":"This workflow requires Kubernetes v1.34.2 or later, an NVIDIA GPU driver version 580 or later","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}