{"resourceId":"nim-operator-312-dynamo-experimental","versions":[{"version":"external-db6857f47a131c6de2802863c5db17a38cd06acee8429d702044257a2e03365f","resource":{"id":"nim-operator-312-dynamo-experimental","title":"NIM Operator 3.1.2 Dynamo integration remains experimental—preview only, not recommended for production","organization":"NVIDIA","sector":"Kubernetes inference operators","geography":"Global (vendor docs)","publishedAt":"NIM Operator 3.1.2 Dynamo experimental docs (page undated; inspected 2026-09-27)","publicationDate":null,"eventDate":"2026-09-27","sourceName":"NVIDIA NIM Operator Documentation","sourceLabel":"Vendor documentation (experimental feature)","sourceUrl":"https://docs.nvidia.com/nim-operator/3.1.2/dynamo.html","evidenceClass":"vendor-claim","outcomeClass":"cautionary","topics":["infrastructure","operating-model","governance-procurement"],"finding":"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.","sledRelevance":"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":"Opened Dynamo (Experimental) doc for 3.1.2; explicit non-production recommendation; enable flag and CRD version notes.","architectureImplications":"Production NIM serving should use supported Operator paths; Dynamo via Operator belongs in non-prod until GA support.","governanceImplications":"Change boards should reject experimental Operator Dynamo as a production dependency without waiver.","securityPrivacyImplications":"Deprecated kube-rbac-proxy image callout is an immediate hardening task if the preview is enabled.","caveats":"Vendor docs; experimental status can change; CRD v0.9.0 via Operator may lag standalone Dynamo releases.","streamIds":["nvidia"],"roles":{"sales":"Lead with a hard boundary: NIM Operator's Dynamo path is explicitly experimental and not recommended for production. It can support lab demos of disaggregated inference under the Operator, but it is not a SLED production commitment. Pair this message with the Enterprise Dynamo 1.4.2 pin discussion so buyers do not conflate screenshots with support. Unsupported claims include production SLAs on Operator-managed Dynamo CRDs or equating experimental status with Enterprise support.","engineering":"Fit only for test clusters with dynamo.enabled=true and accepted break-glass risk. Keep production NIMServices on supported Operator modes. Prerequisites include Operator 3.1.2, replacement of the deprecated kube-rbac-proxy image called out in the docs, and NGC secrets. Constraints include no OpenShift support yet per the page and possible API churn. Proof of value is a working preview namespace plus production admission policies that deny Dynamo CRDs outside that lab path.","delivery":"Work is either to stand up a clearly labeled preview namespace or to document an explicit prohibition. Dependencies include Helm values discipline and a policy engine. Ownership belongs to platform SRE. Skills adoption focuses on experimental feature-flag hygiene and values overlay separation. Governance requires a waiver before any promotion from non-prod to prod. Acceptance is production clusters showing Dynamo CRDs absent or disabled. Risks include accidental enablement through shared values files."},"roleDetails":{"sales":{"customerProblem":"Buyers conflate Operator Dynamo screenshots with supported production architecture.","stakeholders":["platform engineering","security","procurement"],"discoveryQuestions":["Is Dynamo required for the RFP?","Lab or production?","Who accepts experimental risk?"],"valueHypothesis":"Clear experimental labeling prevents unsupported commitments and focuses deals on supported NIM paths.","potentialEngagement":"Architecture boundary workshop: supported NIM vs experimental Dynamo.","unsupportedClaims":["Operator Dynamo is production-supported","Experimental equals Enterprise-supported"]},"engineering":{"fit":"Preview-only Operator Dynamo on non-prod.","architectureIntegration":"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.","proofOfValue":["Preview demo in lab","Prod admission deny rule"]},"delivery":{"work":"Enforce overlay separation; educate app teams.","dependencies":["GitOps","policy controls","training"],"ownership":"Platform SRE.","skillsAdoption":"Train on experimental feature flags.","governanceCheckpoints":["Values review","prod enablement waiver board"],"acceptanceCriteria":["Prod Dynamo CRDs disabled","lab documented"],"risks":["Shared values leaking enablement"]}},"retrievedAt":"2026-09-28T02:59:37Z","enrichedAt":"2026-09-28T03:06:44Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Call experimental status out in runbooks so on-call staff do not treat unsupported flags as prod fixes.","procurementImplications":"RFPs should distinguish supported NIM Operator features from experimental Dynamo.","operatingModelImplications":"Maintain an experimental-features register with expiry/review dates.","sourceVerification":{"openedUrl":"https://docs.nvidia.com/nim-operator/3.1.2/dynamo.html","referenceExcerpt":"not recommended for production use cases","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}