Working with Dynamo Kubernetes Operator — NVIDIA Dynamo Documentation
Title: Working with Dynamo Kubernetes Operator#
URL Source: https://docs.nvidia.com/dynamo/latest/kubernetes/dynamo_operator.html
Published Time: Fri, 07 Nov 2025 17:51:35 GMT
Markdown Content: Overview#
Dynamo operator is a Kubernetes operator that simplifies the deployment, configuration, and lifecycle management of DynamoGraphs. It automates the reconciliation of custom resources to ensure your desired state is always achieved. This operator is ideal for users who want to manage complex deployments using declarative YAML definitions and Kubernetes-native tooling.
Architecture#
-
Operator Deployment: Deployed as a Kubernetes
Deploymentin a specific namespace. -
Controllers:
-
DynamoGraphDeploymentController: WatchesDynamoGraphDeploymentCRs and orchestrates graph deployments. -
DynamoComponentDeploymentController: WatchesDynamoComponentDeploymentCRs and handles individual component deployments.
-
-
Workflow:
-
A custom resource is created by the user or API server.
-
The corresponding controller detects the change and runs reconciliation.
-
Kubernetes resources (Deployments, Services, etc.) are created or updated to match the CR spec.
-
Status fields are updated to reflect the current state.
-
Custom Resource Definitions (CRDs)#
For the complete technical API reference for Dynamo Custom Resource Definitions, see:
Installation#
Quick Install with Helm#
Set environment
export NAMESPACE=dynamo-system export RELEASE_VERSION=0.x.x # any version of Dynamo 0.3.2+ listed at https://github.com/ai-dynamo/dynamo/releases
Install Platform (includes operator)
helm fetch https://helm.ngc.nvidia.com/nvidia/ai-dynamo/charts/dynamo-platform-${RELEASE_VERSION}.tgz helm install dynamo-platform dynamo-platform-${RELEASE_VERSION}.tgz --namespace ${NAMESPACE} --create-namespace
For namespace-restricted installations (shared clusters), you’ll need to install the Dynamo platform in each namespace you want to deploy to. Namespace restriction is enabled by setting the dynamo-operator.namespaceRestriction.enabled flag to true.
helm install dynamo-platform dynamo-platform-${RELEASE_VERSION}.tgz
--namespace ${NAMESPACE}
--create-namespace
--set dynamo-operator.namespaceRestriction.enabled=true
Building from Source#
Set environment
export NAMESPACE=dynamo-system export DOCKER_SERVER=your-registry.com/ # your container registry export IMAGE_TAG=latest
Build operator image
cd deploy/cloud/operator docker build -t $DOCKER_SERVER/dynamo-operator:$IMAGE_TAG . docker push $DOCKER_SERVER/dynamo-operator:$IMAGE_TAG cd -
Install CRDs
cd deploy/cloud/helm helm install dynamo-crds ./crds/ --namespace default
Install platform with custom operator image
helm install dynamo-platform ./platform/
--namespace ${NAMESPACE}
--create-namespace
--set "dynamo-operator.controllerManager.manager.image.repository=${DOCKER_SERVER}/dynamo-operator"
--set "dynamo-operator.controllerManager.manager.image.tag=${IMAGE_TAG}"
For detailed installation options, see the Installation Guide
Development#
- Code Structure:
The operator is built using Kubebuilder and the operator-sdk, with the following structure:
-
controllers/: Reconciliation logic -
api/v1alpha1/: CRD types -
config/: Manifests and Helm charts
References#
Links/Buttons: