Add Dynamo and NVCF responsibility boundary diagram
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 218
- Forks
- 72
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 427
Description
Add a reusable SVG that documents the deployment and routing responsibility boundary between NVCF, NVCA, Kubernetes, the Dynamo Operator, Grove/KAI, and the Dynamo runtime. The diagram should distinguish multi-cluster routing from in-cluster routing and show how worker readiness and deployment status flow back through NVCA and NVCF.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by mapping the responsibility boundary among NVCF, NVCA, Kubernetes, the Dynamo Operator, Grove/KAI, and the Dynamo runtime. Produce a reusable SVG that distinguishes multi-cluster from in-cluster routing and shows worker-readiness and deployment-status flow back through NVCA and NVCF.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- cloud, documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100