From the NVIDIA edition of September 19, 2026
AI Enterprise Infra 8.2 support matrix pins operators and Government Ready columns
NVIDIA · Enterprise AI infrastructure software · Global (enterprise/gov packaging)
- Publisher
- NVIDIA AI Enterprise Documentation
- Original publication
- undated 8.2 matrix page (companion to Infra 8.2)
- Source retrieved
- 2026-09-20
What happened
The version-pinned AI Enterprise Infra 8.2 support matrix lists component versions and a Government Ready column: Data Center GPU Driver 595.91.07, Fabric Manager 595.91.07, GPU Operator 26.3.3 (Supported for Gov Ready with footnote to operand list; ARM N/A for Gov Ready), Network Operator 26.4.1, NIM Operator 3.1.2 (Supported across x86/ARM/Gov Ready), DOCA networking 3.4.0 Supported for Gov Ready, Run:ai 2.26, BCM 11.33.1. Platform tables include HGX/DGX B200/B300 and GB200/GB300 NVL72 bare-metal notes, OpenShift 4.18–4.22, Kubernetes 1.32–1.36, and cloud instance matrices. Footnotes restrict some HGX vGPU/KubeVirt combinations.
Why it matters
Actionable for SLED regulated Kubernetes baselines: yesterday 8.2 release notes are complemented by the matrix Government Ready flags and orchestration/OS pins needed for ATO-oriented stacks. Does not itself confer FedRAMP authorization.
Evidence and measured results
Table 4 infrastructure software with Gov Ready column; Kubernetes bare-metal and virtualized tables; GB200/GB300 bare-metal-only notes; footnotes pointing to Gov Ready operand docs; vSphere HGX B200/B300 1:1 and multi-vGPU only (no fractional).
Limitations and uncertainty
Vendor matrix; undated page body; Gov Ready footnotes defer to other docs; some cells N/A.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-20; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Regulated buyers need version-pinned, Gov Ready-aware BOMs—not vague enterprise bundles.
- Stakeholders
- platform
- security/compliance
- procurement
- Discovery questions
- Which matrix row is your target orchestration?
- Do you require Gov Ready operands?
- Bare-metal NVL72 or virtualized?
- Value hypothesis
- An 8.2 matrix-conformant stack reduces support and compliance ambiguity for NVIDIA AI Enterprise.
- Potential engagement
- BOM conformance review against 8.2 matrix plus Gov Ready footnotes.
- Unsupported claims
- Matrix equals FedRAMP ATO
- All components Gov Ready
- Fractional vGPU on HGX B200/B300 vSphere
Pre-sales engineering
Role takeaway
- Fit
- Any AI Enterprise Infra 8.2 deployment planning upgrade or greenfield.
- Architecture and integration
- Pin drivers/operators/orchestrators per tables; respect bare-metal NVL72 notes.
- Prerequisites
- current inventory
- NGC entitlement
- Gov Ready operand list if required
- Constraints
- Footnote-deferred Gov Ready details
- HGX virtualization limits
- ARM Gov Ready N/A on GPU Operator
- Security
- Treat Gov Ready as necessary but not sufficient for system authorization.
- Proof of value
- Inventory matches pins
- Smoke tests on supported OS/K8s
- Gov Ready images pull successfully
Delivery
Role takeaway
- Work
- Version-pin upgrade runbook and validation matrix.
- Dependencies
- NVIDIA entitlement
- OS vendor
- security reviewers
- Ownership
- Platform engineering lead.
- Skills and adoption
- Ops must read support matrix footnotes, not only release-note headlines.
- Governance checkpoints
- No unsupported orchestration versions
- Gov Ready scope documented
- vGPU mode restrictions checked
- Acceptance criteria
- Pins verified
- Workloads healthy
- Exception log empty or approved
- Risks
- Silent drift from pins
- Virtualization mode mismatch
- Authorization assumed
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Pin operator/driver versions to 8.2 matrix before claiming support; GB300 NVL72 paths are bare-metal scoped in matrix; Gov Ready ARM gaps matter for Grace hosts.
Governance
Who approves, reviews and stays accountable for outcomes?
Use matrix as compliance inventory input; still need host FIPS/STIG and system ATO controls outside this page.
Security and privacy
What data, permissions and controls need testing?
Gov Ready column is packaging designation; not a completed authorization.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
None stated.
Procurement
What should contracts, pricing and exit terms secure?
Write 8.2 matrix pins into contracts and acceptance tests.
Operating model
Which teams own the service once it runs?
Supportability becomes a continuous pin-management practice.
Publication history
- 2026-09-19NVIDIA · Issue 148 resources
Stable resource ID: nvidia-aie-82-support-matrix-2026