Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the NVIDIA edition of September 27, 2026

Vendor claimCautionaryUndated source

NIM Operator 3.1.2 Dynamo integration remains experimental—preview only, not recommended for production

NVIDIA · Kubernetes inference operators · Global (vendor docs)

NVIDIA
Publisher
NVIDIA NIM Operator Documentation
Original publication
NIM Operator 3.1.2 Dynamo experimental docs (page undated; inspected 2026-09-27)
Source retrieved
2026-09-28
Event date
2026-09-27
Read original source

What happened

The NIM Operator 3.1.2 Dynamo page states the Dynamo CRD deployment feature is experimental, not fully supported, included as a preview for testing environments, and not recommended for production; APIs may change. Enabling requires Helm dynamo.enabled=true; docs note Dynamo CRDs v0.9.0, upstream Kubernetes support with OpenShift planned later, and a deprecated default kube-rbac-proxy image needing replacement.

Why it matters

SLED platforms combining NIM Operator with Dynamo should keep this path in lab/preview until support posture changes—aligns with Enterprise Dynamo 1.4.2 pin caution.

Evidence and measured results

Opened Dynamo (Experimental) doc for 3.1.2; explicit non-production recommendation; enable flag and CRD version notes.

Limitations and uncertainty

Vendor docs; experimental status can change; CRD v0.9.0 via Operator may lag standalone Dynamo releases.

Cross-source patterns this evidence supports

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-28; 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 Operator Dynamo screenshots with supported production architecture.
Stakeholders
  • platform engineering
  • security
  • procurement
Discovery questions
  • Is Dynamo required for the RFP?
  • Lab or production?
  • Who accepts experimental risk?
Value hypothesis
Clear experimental labeling prevents unsupported commitments and focuses deals on supported NIM paths.
Potential engagement
Architecture boundary workshop: supported NIM vs experimental Dynamo.
Unsupported claims
  • Operator Dynamo is production-supported
  • Experimental equals Enterprise-supported

Pre-sales engineering

Role takeaway
Fit
Preview-only Operator Dynamo on non-prod.
Architecture and integration
Separate values/overlays; deny in prod admission; patch kube-rbac-proxy image if enabled.
Prerequisites
  • Operator 3.1.2
  • policy engine
  • NGC pull
Constraints
  • Not recommended for production
  • API changes possible
  • OpenShift not yet
Security
Replace deprecated proxy image; limit RBAC blast radius.
Proof of value
  • Preview demo in lab
  • Prod admission deny rule

Delivery

Role takeaway
Work
Enforce overlay separation; educate app teams.
Dependencies
  • GitOps
  • policy controls
  • training
Ownership
Platform SRE.
Skills and adoption
Train on experimental feature flags.
Governance checkpoints
  • Values review
  • prod enablement waiver board
Acceptance criteria
  • Prod Dynamo CRDs disabled
  • lab documented
Risks
  • Shared values leaking enablement

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?

Production NIM serving should use supported Operator paths; Dynamo via Operator belongs in non-prod until GA support.

Governance

Who approves, reviews and stays accountable for outcomes?

Change boards should reject experimental Operator Dynamo as a production dependency without waiver.

Security and privacy

What data, permissions and controls need testing?

Deprecated kube-rbac-proxy image callout is an immediate hardening task if the preview is enabled.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Call experimental status out in runbooks so on-call staff do not treat unsupported flags as prod fixes.

Procurement

What should contracts, pricing and exit terms secure?

RFPs should distinguish supported NIM Operator features from experimental Dynamo.

Operating model

Which teams own the service once it runs?

Maintain an experimental-features register with expiry/review dates.

Publication history

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

Stable resource ID: nim-operator-312-dynamo-experimental