DGDR
An intent-driven deployment request resource in Dynamo. The user declares only the model, backend, workload, hardware, and optional SLA targets, and the system automatically derives and generates the DynamoGraph Deployment topology.
Timeline (last 90 days)
DGDR (DynamoGraph Deployment Request) is an intent-driven deployment path: users only need to describe the model, backend, workload, hardware, and optional SLA targets, and Dynamo analyzes these inputs and generates a DynamoGraph Deployment (DGD).
The five-step DGDR workflow is: define the DGDR → apply it with kubectl → wait for the Operator to create and reconcile the DGD → send requests to the API endpoint → verify that responses come from the Dynamo endpoint.
For teams migrating a small existing endpoint, it is recommended to start with DGDR to get end-to-end running, verify that the OpenAI-compatible endpoint works, and then adjust the deployment according to capacity needs, rather than refactoring the entire stack.
The rule for choosing between DGDR and DGD: choose DGDR if you want a usable endpoint quickly and do not want to hand-write the topology; use DGD directly if you already have a validated recipe and need fine-grained control over the inference graph.
All Facts (4)
DGDR (DynamoGraph Deployment Request) is an intent-driven deployment path: users only need to describe the model, backend, workload, hardware, and optional SLA targets, and Dynamo analyzes these inputs and generates a DynamoGraph Deployment (DGD).
50%UnverifiedFor teams migrating a small existing endpoint, it is recommended to start with DGDR to get end-to-end running, verify that the OpenAI-compatible endpoint works, and then adjust the deployment according to capacity needs, rather than refactoring the entire stack.
50%UnverifiedThe rule for choosing between DGDR and DGD: choose DGDR if you want a usable endpoint quickly and do not want to hand-write the topology; use DGD directly if you already have a validated recipe and need fine-grained control over the inference graph.
50%UnverifiedThe five-step DGDR workflow is: define the DGDR → apply it with kubectl → wait for the Operator to create and reconcile the DGD → send requests to the API endpoint → verify that responses come from the Dynamo endpoint.
50%