Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fix: do not set resources by default
  • Loading branch information
julienmancuso committed Aug 18, 2025
commit 4b71d2bb636504456a9c0195d7fe0fa76ba7fef9
7 changes: 1 addition & 6 deletions docs/guides/dynamo_deploy/multinode-deployment.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Dynamo supports multinode deployments through the `multinode` section in resourc

For sophisticated multinode deployments, Dynamo integrates with advanced Kubernetes orchestration systems:

- **[Grove](https://github.com/NVIDIA/grove)**: Network topology-aware gang scheduling and auto-scaling for AI workloads
- **[Grove](https://github.com/NVIDIA/grove/blob/main/docs/getting-started.md)**: Network topology-aware gang scheduling and auto-scaling for AI workloads
- (optional) **[KAI-Scheduler](https://github.com/NVIDIA/KAI-Scheduler)**: Kubernetes native scheduler optimized for AI workloads at scale

These systems provide enhanced scheduling capabilities including topology-aware placement, gang scheduling, and coordinated auto-scaling across multiple nodes.
Expand Down Expand Up @@ -66,12 +66,7 @@ The `multinode` section in a resource specification defines how many physical no
multinode:
nodeCount: 2
resources:
requests:
cpu: "10"
memory: "40Gi"
limits:
cpu: "10"
memory: "40Gi"
gpu: "2" # 2 GPUs per node
```

Expand Down
Loading