Skip to content

GitLab

"...ssh:/git@developer.sourcefind.cn:2222/OpenDAS/dynamo.git" did not exist on "92f06b0e7ff03bd02cc6a56f9ba9258917dc9dae"
Unverified Commit 4eae238f authored by julienmancuso's avatar julienmancuso Committed by GitHub
Browse files

feat: add dynamo operator overview doc (#688)

parent 33e72720
Hide whitespace changes
Inline Side-by-side
Showing with 284 additions and 1 deletion
docs/guides/dynamo_deploy/dynamo_cloud.md
View file @ 4eae238f
...@@ -23,7 +23,7 @@ The Dynamo Cloud platform is a comprehensive solution for deploying and managing ...@@ -23,7 +23,7 @@ The Dynamo Cloud platform is a comprehensive solution for deploying and managing
The Dynamo cloud platform consists of several key components: The Dynamo cloud platform consists of several key components:
- **Dynamo Operator**: A Kubernetes operator that manages the lifecycle of Dynamo inference graphs from build ➡️ deploy. - **Dynamo Operator**: A Kubernetes operator that manages the lifecycle of Dynamo inference graphs from build ➡️ deploy. For more information on the operator, see the [Dynamo Operator Page](dynamo_operator.md).
- **API Store**: Stores and manages service configurations and metadata related to Dynamo deployments. Needs to be exposed externally. - **API Store**: Stores and manages service configurations and metadata related to Dynamo deployments. Needs to be exposed externally.
- **Custom Resources**: Kubernetes custom resources for defining and managing Dynamo services - **Custom Resources**: Kubernetes custom resources for defining and managing Dynamo services
......
docs/guides/dynamo_deploy/dynamo_operator.md 0 → 100644
View file @ 4eae238f
# Dynamo Kubernetes Operator Documentation
## 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.
---
## Table of Contents
- [Overview](#overview)
- [Architecture](#architecture)
- [Custom Resource Definitions (CRDs)](#custom-resource-definitions-crds)
- [Installation](#installation)
- [Usage](#usage)
- [Examples](#examples)
- [Reconciliation Logic](#reconciliation-logic)
- [Configuration](#configuration)
- [Troubleshooting](#troubleshooting)
- [Development](#development)
- [References](#references)
---
## Architecture
- **Operator Deployment:**
Deployed as a Kubernetes `Deployment` in a specific namespace.
- **Controllers:**
- `DynamoGraphDeploymentController`: Watches `DynamoGraphDeployment` CRs and orchestrates graph deployments.
- `DynamoComponentDeploymentController`: Watches `DynamoComponentDeployment` CRs and handles individual component deployments.
- `DynamoComponentController`: Watches `DynamoComponent` CRs and manages image builds and artifact tracking.
- **Workflow:**
1. A custom resource is created by the user or API server.
2. The corresponding controller detects the change and runs reconciliation.
3. Kubernetes resources (Deployments, Services, etc.) are created or updated to match the CR spec.
4. Status fields are updated to reflect the current state.
---
## Custom Resource Definitions (CRDs)
### CRD: `DynamoGraphDeployment`
| Field | Type | Description | Required | Default |
|------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------|----------|---------|
| `dynamoComponent`| string | Reference to the dynamoComponent identifier | Yes | |
| `services` | map | Map of service names to runtime configurations. This allows the user to override the service configuration defined in the DynamoComponentDeployment. | No | |
**API Version:** `nvidia.com/v1alpha1`
**Scope:** Namespaced
#### Example
```yaml
apiVersion: nvidia.com/v1alpha1
kind: DynamoGraphDeployment
metadata:
name: disagg
spec:
dynamoComponent: frontend:jh2o6dqzpsgfued4
envs:
- name: GLOBAL_ENV_VAR
value: some_global_value
services:
Frontend:
replicas: 1
envs:
- name: SPECIFIC_ENV_VAR
value: some_specific_value
Processor:
replicas: 1
envs:
- name: SPECIFIC_ENV_VAR
value: some_specific_value
VllmWorker:
replicas: 1
envs:
- name: SPECIFIC_ENV_VAR
value: some_specific_value
PrefillWorker:
replicas: 1
envs:
- name: SPECIFIC_ENV_VAR
value: some_specific_value
Router:
replicas: 0
envs:
- name: SPECIFIC_ENV_VAR
value: some_specific_value
```
---
### CRD: `DynamoComponentDeployment`
| Field | Type | Description | Required | Default |
|--------------------|----------|---------------------------------------------------------------|----------|---------|
| `dynamoNamespace` | string | Namespace of the DynamoComponent | Yes | |
| `dynamoComponent` | string | Name of the dynamoComponent artifact | Yes | |
| `dynamoTag` | string | FQDN of the service to run | Yes | |
| `serviceName` | string | Logical name of the service being deployed | Yes | |
| `envs` | array | Environment variables for runtime | No | `[]` |
| `externalServices`| map | External service dependencies | No | |
| `annotations` | map | Additional metadata annotations for the pod | No | |
| `labels` | map | Custom labels applied to the deployment and pod | No | |
| `resources` | object | Resource limits and requests (CPU, memory, GPU) | No | |
| `autoscaling` | object | Autoscaling rules for the deployment | No | |
| `envFromSecret` | string | Reference to a secret for injecting env vars | No | |
| `pvc` | object | Persistent volume claim configuration | No | |
| `ingress` | object | Ingress configuration for exposing the service | No | |
| `extraPodMetadata`| object | Additional labels and annotations for the pod | No | |
| `extraPodSpec` | object | Custom PodSpec fields to merge into the generated pod | No | |
| `livenessProbe` | object | Kubernetes liveness probe | No | |
| `readinessProbe` | object | Kubernetes readiness probe | No | |
| `replicas` | int | Number of replicas to run | No | `1` |
**API Version:** `nvidia.com/v1alpha1`
**Scope:** Namespaced
#### Example
```yaml
apiVersion: nvidia.com/v1alpha1
kind: DynamoComponentDeployment
metadata:
name: test-41fa991-vllmworker
spec:
dynamoNamespace: dynamo
dynamoComponent: frontend:jh2o6dqzpsgfued4
dynamoTag: graphs.disagg:Frontend
envs:
- name: DYN_DEPLOYMENT_CONFIG
value: '<long JSON config>'
externalServices:
PrefillWorker:
deploymentSelectorKey: dynamo
deploymentSelectorValue: PrefillWorker/dynamo
resources:
limits:
cpu: "10"
gpu: "1"
memory: 20Gi
requests:
cpu: "500m"
gpu: "1"
memory: 20Gi
serviceName: Frontend
```
---
### CRD: `DynamoComponent`
| Field | Type | Description | Required | Default |
|---------------------------------|--------------------------|--------------------------------------------------------------------------------------|----------|---------|
| `dynamoComponent` | string | Name of the dynamoComponent artifact | Yes | |
| `image` | string | Custom container image. If not specified, an image will be built | No | |
| `imageBuildTimeout` | Duration | Timeout duration for the image building process | No | |
| `buildArgs` | []string | Additional arguments to pass to the container image build process | No | |
| `imageBuilderExtraPodMetadata` | ExtraPodMetadata | Additional metadata to add to the image builder pod | No | |
| `imageBuilderExtraPodSpec` | ExtraPodSpec | Additional pod spec configurations for the image builder pod | No | |
| `imageBuilderExtraContainerEnv` | []EnvVar | Additional environment variables for the image builder container | No | |
| `imageBuilderContainerResources`| ResourceRequirements | Resource requirements (CPU, memory) for the image builder container | No | |
| `imagePullSecrets` | []LocalObjectReference | Secrets required for pulling private container images | No | |
| `dockerConfigJsonSecretName` | string | Name of the secret containing Docker registry credentials | No | |
| `downloaderContainerEnvFrom` | []EnvFromSource | Environment variables to be sourced for the downloader container | No | |
**API Version:** `nvidia.com/v1alpha1`
**Scope:** Namespaced
#### Example
```yaml
apiVersion: nvidia.com/v1alpha1
kind: DynamoComponent
metadata:
name: frontend--jh2o6dqzpsgfued4
spec:
dynamoComponent: frontend:jh2o6dqzpsgfued4
```
---
## Installation
[See installation steps](dynamo_cloud.md#deployment-steps)
---
## Deploying a Dynamo Pipeline using the Operator
[See deployment steps](operator_deployment.md)
---
## Reconciliation Logic
### DynamoGraphDeployment
- **Actions:**
- Create a DynamoComponent CR to build the docker image
- Create a DynamoComponentDeployment CR for each component defined in the Dynamo graph being deployed
- **Status Management:**
- `.status.conditions`: Reflects readiness, failure, progress states
- `.status.state`: overall state of the deployment, based on the state of the DynamoComponentDeployments
### DynamoComponentDeployment
- **Actions:**
- Create a Deployment, Service, and Ingress for the service
- **Status Management:**
- `.status.conditions`: Reflects readiness, failure, progress states
### DynamoComponent
- **Actions:**
- Create a job to build the docker image
- **Status Management:**
- `.status.conditions`: Reflects readiness, failure, progress states
---
## Configuration
- **Environment Variables:**
| Name | Description | Default |
|----------------------------------------------------|--------------------------------------|--------------------------------------------------------|
| `ADD_NAMESPACE_PREFIX_TO_IMAGE_NAME` | Adds namespace prefix to image names | `false` |
| `DYNAMO_IMAGE_BUILD_ENGINE` | Engine used for building images | `buildkit` |
| `BUILDKIT_URL` | BuildKit daemon URL | `tcp://dynamo-platform-dynamo-operator-buildkitd:1234` |
| `DOCKER_REGISTRY_DYNAMO_COMPONENTS_REPOSITORY_NAME`| Repository name for dynamo images | `dynamo-components` |
| `DOCKER_REGISTRY_SECURE` | Use secure connection for registry | `true` |
| `DOCKER_REGISTRY_SERVER` | Docker registry server address | `nvcr.io/nvidian/dynamo` |
| `DOCKER_REGISTRY_USERNAME` | Registry authentication username | `username` |
| `ESTARGZ_ENABLED` | Enable eStargz image optimization | `false` |
| `INTERNAL_IMAGES_BUILDKIT` | BuildKit image | `moby/buildkit:v0.20.2` |
| `LOG_LEVEL` | Logging verbosity level | `info` |
| `API_STORE_ENDPOINT` | Api store service endpoint | `http://dynamo-store` |
| `DYNAMO_IMAGE_BUILDER_NAMESPACE` | Namespace for image building | `dynamo` |
| `DYNAMO_SYSTEM_NAMESPACE` | System namespace | `dynamo` |
- **Flags:**
| Flag | Description | Default |
|-----------------------|--------------------------------------------|---------|
| `--natsAddr` | Address of NATS server | "" |
| `--etcdAddr` | Address of etcd server | "" |
---
## Troubleshooting
| Symptom | Possible Cause | Solution |
|------------------------|-------------------------------|-----------------------------------|
| Resource not created | RBAC missing | Ensure correct ClusterRole/Binding|
| Status not updated | CRD schema mismatch | Regenerate CRDs with kubebuilder |
| Image build hangs | Misconfigured DynamoComponent | Check image build logs |
---
## 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
- [Kubernetes Operator Pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/)
- [Custom Resource Definitions](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)
- [Operator SDK](https://sdk.operatorframework.io/)
- [Helm Best Practices for CRDs](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/)
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment