Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the NVIDIA edition of September 22, 2026

Standards or public-body guidanceCautionaryUndated source

NIM Operator 3.1.1 Dynamo path is experimental and not production-supported

NVIDIA · Kubernetes AI operators / NIM deployment · Global (upstream Kubernetes; OpenShift later)

NVIDIA
Publisher
NVIDIA NIM Operator Documentation
Original publication
undated docs page (NIM Operator 3.1.1)
Source retrieved
2026-09-23
Event date
2026-09-22
Read original source

What happened

NIM Operator 3.1.1 documents a Dynamo integration enabled with dynamo.enabled=true that deploys Dynamo CRDs (noted as v0.9.0) and management pods. The page warns the feature is experimental, not fully supported, preview-oriented, and not recommended for production; APIs may change. Support is described for upstream-compatible Kubernetes, with OpenShift planned later. Install guidance requires NGC pull and API secrets plus an HF token secret, and notes the default kube-rbac-proxy image repository in the Dynamo v0.9.0 chart has been deprecated and must be overridden.

Why it matters

Warns SLED buyers that NIM Operator + Dynamo is not yet a supported production procurement path—useful when vendors pitch a unified NIM/Dynamo operator story after Dynamo 1.5 GA.

Evidence and measured results

Explicit experimental/not fully supported/not for production warning; dynamo.enabled=true Helm flag; deploys Dynamo CRDs v0.9.0; upstream Kubernetes only (OpenShift later); requires ngc-secret, ngc-api-secret, hf-token-secret; kube-rbac-proxy image deprecated and needs override; sample Qwen vLLM agg frontend curls on :8000.

Limitations and uncertainty

Docs page undated beyond version 3.1.1; CRD v0.9.0 may lag Dynamo 1.5.0 CRD story; example only, not measured campus outcomes.

Cross-source patterns this evidence supports

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-23; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
Buyers conflate NIM Operator marketing with a supported Dynamo production path.
Stakeholders
  • AI platform
  • procurement
  • security
Discovery questions
  • Do you need production support today?
  • OpenShift or upstream Kubernetes?
  • Is this a lab spike or a campus go-live?
Value hypothesis
Preview can inform a later supported design without committing production risk now.
Potential engagement
Architecture decision record separating preview vs supported Dynamo paths.
Unsupported claims
  • Production-supported NIM Operator Dynamo
  • OpenShift ready
  • CRDs match Dynamo 1.5 GA

Pre-sales engineering

Role takeaway
Fit
Lab only while experimental warning stands.
Architecture and integration
NIM Operator Helm subchart enabling Dynamo CRDs/management pods.
Prerequisites
  • NGC secrets
  • HF token
  • upstream Kubernetes
  • proxy image override
Constraints
  • Experimental API churn
  • No OpenShift
  • CRD v0.9.0 note
Security
Replace deprecated kube-rbac-proxy; lock secrets to sandbox NS.
Proof of value
  • Qwen sample chat works
  • Proxy image overridden
  • Namespace isolated

Delivery

Role takeaway
Work
Sandbox install/uninstall with written non-prod banner.
Dependencies
  • NGC access
  • HF token
  • cluster admin for CRDs
Ownership
Platform sandbox owner.
Skills and adoption
Operators learn Dynamo CRDs without prod pressure.
Governance checkpoints
  • No prod namespace
  • Support ticket path undefined = stop
  • Expiry date on spike
Acceptance criteria
  • Sample healthy
  • Deprecated image gone
  • Teardown complete
Risks
  • Preview promoted by mistake
  • CRD conflict with Dynamo Platform
  • Secret sprawl

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?

Keep production Dynamo on the Dynamo Platform/Operator path validated for your release; treat NIM Operator Dynamo as a lab preview until support language changes.

Governance

Who approves, reviews and stays accountable for outcomes?

Do not accept NIM Operator Dynamo as meeting production support or FedRAMP-path evidence without a later supported matrix entry.

Security and privacy

What data, permissions and controls need testing?

Deprecated kube-rbac-proxy image is an immediate supply-chain patch item; NGC/HF secrets expand the credential surface.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

None claimed; preview path does not change end-user accessibility posture.

Procurement

What should contracts, pricing and exit terms secure?

Do not write NIM Operator Dynamo into production SOWs while experimental language remains.

Operating model

Which teams own the service once it runs?

Maintain two tracks: supported Dynamo Platform vs NIM Operator preview.

Publication history

  1. 2026-09-22NVIDIA · Issue 178 resources
Read preserved resource versions (JSON)

Stable resource ID: nvidia-nim-operator-dynamo-experimental-311