fix(self-managed-stack): bump llm-request-router pin to 1.6.6#249
Open
Max-NV wants to merge 1 commit into
Open
fix(self-managed-stack): bump llm-request-router pin to 1.6.6#249Max-NV wants to merge 1 commit into
Max-NV wants to merge 1 commit into
Conversation
Move the self-managed stack from chart 1.6.3 to 1.6.6, picking up the stargate 0.3.2 image and the --backend-connectivity=reverse fix together. Chart 1.6.5 alone (stargate 0.3.2 without the flag) crash-loops the router; 1.6.6 renders --backend-connectivity=reverse with the reverse-tunnel address so the pod starts cleanly. NVBUG-6469041
📝 WalkthroughWalkthroughThe self-managed Helmfile updates the ChangesLLM request router chart update
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
FamousDirector
approved these changes
Jul 17, 2026
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@deploy/stacks/self-managed/helmfile.d/02-core.yaml.gotmpl`:
- Line 158: Update the user-facing manifest entry for
helm-nvcf-llm-request-router in docs/user/manifest.md from version 1.6.3 to
1.6.6, matching the version pinned in the Helmfile.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 795a65b8-8cfb-47fa-8c7f-637205f70b36
📒 Files selected for processing (1)
deploy/stacks/self-managed/helmfile.d/02-core.yaml.gotmpl
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The self-managed stack pinned llm-request-router chart 1.6.3 (stargate image 0.3.0). The 0.3.2 image adds a
--backend-connectivitygate; chart 1.6.5 took the 0.3.2 image without passing the flag and crash-loops the router. Chart 1.6.6 (#248) passes--backend-connectivity=reverse.What changed
Bump the llm-request-router pin 1.6.3 -> 1.6.6 in the self-managed core helmfile, picking up the stargate 0.3.2 image and the crashloop fix together. Keeps main-line (0.7.0) from regressing into the same crashloop when it moves onto the 0.3.2 image.
References
NVBUG-6469041
Chart fix: #248
Summary by CodeRabbit