Repository navigation
Conversation
Signed-off-by: Thomas Montfort <tjmontfort12@gmail.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. WalkthroughThe namespace argument parser now reads ChangesWorker namespace suffix
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The namespace suffix behavior is scoped to the shared parser and no actionable merge risk was identified. 🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
Full details: Description checkExplanation The description explains the change and validation, but it does not follow the required template. It omits the Overview, Details, Where should the reviewer start?, and required Related Issues sections.
Comment |
Signed-off-by: Thomas Montfort <tjmontfort12@gmail.com>
| long, | ||
| default_value = "dynamo", | ||
| env = "DYN_NAMESPACE", | ||
| value_parser = parse_worker_namespace |
There was a problem hiding this comment.
Operator upgrade workloads can supply an already-suffixed DYN_NAMESPACE together with DYN_NAMESPACE_WORKER_SUFFIX (for example, default-qwen-decode-<hash> and <hash> in deploy/operator/internal/controller/upgrade_test.go). Applying this value parser unconditionally turns that into default-qwen-decode-<hash>-<hash>, while the controller's published runtime namespace remains suffixed once. Rust sidecars then register outside the namespace used for the active worker generation. Preserve an already-applied worker suffix, or have the caller provide an unambiguous base namespace before appending.
🤖 AI Fix
Append DYN_NAMESPACE_WORKER_SUFFIX only when the parsed namespace does not already end with the exact hyphen-delimited suffix, and add coverage for an already-suffixed DYN_NAMESPACE.
|
Already implemented in: #14955 |
Pull request was closed
Summary
DYN_NAMESPACE_WORKER_SUFFIXidentifies a worker generation during Kubernetes rolling updates. Appending it to the Dynamo namespace isolates worker generations and prevents cross-generation communication.The Python entrypoint already applies this suffix in the integrated runtime/engine path. Sidecars previously ignored it. This change adds the same behavior to the shared
CommonArgsnamespace parser used by the vLLM, SGLang, and TensorRT-LLM sidecars:<namespace>-<suffix>.This applies to environment-provided, default, and explicit
--namespacevalues.Validation
git diff --checkpass.Summary by CodeRabbit
New Features
Bug Fixes