Deploy and manage Dynamo inference graphs on Kubernetes with automated orchestration and scaling, using the Dynamo Kubernetes Platform.
Determine your cluster environment:
Shared/Multi-Tenant Cluster (K8s cluster with existing Dynamo artifacts):
Dedicated Cluster (full cluster admin access):
Local Development (Minikube, testing):
To check if CRDs already exist:
To check if a cluster-wide operator already exists:
Platform is installed using Dynamo Kubernetes Platform helm chart.
Path A: Pre-built Artifacts
Path B: Custom Build from Source
All helm install commands could be overridden by either setting the values.yaml file or by passing in your own values.yaml:
and/or setting values as flags to the helm install command, as follows:
Verify before proceeding:
Estimated time: 5-30 minutes depending on path
No cluster? See Minikube Setup for local development.
Install from NGC published artifacts.
For Shared/Multi-Tenant Clusters:
If your cluster has namespace-restricted Dynamo operators, you MUST add namespace restriction to your installation:
Note: Use the full path dynamo-operator.namespaceRestriction.enabled=true (not just namespaceRestriction.enabled=true).
If you see this validation error, you need namespace restriction:
For multinode deployments, you need to install multinode orchestration components:
Option 1 (Recommended): Grove + KAI Scheduler
Option 2: LeaderWorkerSet (LWS) + Volcano
See the Multinode Deployment Guide for details on orchestrator selection.
By default, Model Express Server is not used. If you wish to use an existing Model Express Server, you can set the modelExpressURL to the existing server’s URL in the helm install command:
By default, Dynamo Operator is installed cluster-wide and will monitor all namespaces. If you wish to restrict the operator to monitor only a specific namespace (the helm release namespace by default), you can set the namespaceRestriction.enabled to true. You can also change the restricted namespace by setting the targetNamespace property.
Build and deploy from source for customization, contributing to Dynamo, or using the latest features from the main branch.
Note: This gives you access to the latest unreleased features and fixes on the main branch.
Deploy Model/Workflow
Explore Backend Guides
Optional:
“VALIDATION ERROR: Cannot install cluster-wide Dynamo operator”
Cause: Attempting cluster-wide install on a shared cluster with existing namespace-restricted operators.
Solution: Add namespace restriction to your installation:
Note: Use the full path dynamo-operator.namespaceRestriction.enabled=true (not just namespaceRestriction.enabled=true).
CRDs already exist
Cause: Installing CRDs on a cluster where they’re already present (common on shared clusters).
Solution: Skip step 2 (CRD installation), proceed directly to platform installation.
To check if CRDs exist:
Pods not starting?
HuggingFace model access?
Bitnami etcd “unrecognized” image?
This error that you might encounter during helm install is due to bitnami changing their docker repository to a secure one.
just add the following to the helm install command:
Clean uninstall?