Repository navigation
fix(recipes): use default TCP transport for Kimi aggregated KV routing - #15428
Conversation
Signed-off-by: Saravana Periyasamy <saperiyasamy@nvidia.com>
Signed-off-by: Saravana Periyasamy <saperiyasamy@nvidia.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: ai-dynamo/dynamo/.coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 8 remain after this review. WalkthroughThe deployment configuration removes ChangesDeployment arguments
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to The recipe now uses the default TCP request transport for Kimi aggregated KV routing. No concrete merge-blocking risk was identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
Summary
Remove
--request-plane natsfrom the Kimi-K2.5 aggregated Eagle3/KV-router recipe's frontend and worker so both use the default TCP request transport. Preserve the default ZMQ event transport, 24-GPU topology, engine settings, and benchmark.Validation
Related Issues
Related to #15361 and OPS-8639.
Summary by CodeRabbit