fix: fix accidental overwrite

[atchernych]

Overview:

Details:

Where should the reviewer start?

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• closes GitHub issue: #xxx

Summary by CodeRabbit

• Chores
  • Updated container image references in deployment configuration to use new image sources for runtime components.

[coderabbitai]

Walkthrough

Two container image references in a deployment configuration file were updated from an internal GitLab registry to the NVIDIA container registry (nvcr.io). Both the Frontend and VllmDecodeWorker mainContainer specifications now reference the updated image location. No configuration logic or resource definitions were altered.

Changes

Cohort / File(s)	Summary
Container image registry update components/backends/vllm/deploy/agg.yaml	Updated two image references from gitlab-master.nvidia.com:5005/dl/ai-dynamo/dynamo/dynamo:vllm-1029 to nvcr.io/nvidia/ai-dynamo/vllm-runtime:my-tag in Frontend and VllmDecodeWorker mainContainer specs

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Verify the new image URI is correctly formed and accessible
• Confirm the image tag (my-tag) is appropriate for the deployment environment
• Ensure both Frontend and VllmDecodeWorker services are compatible with the updated container image

Poem

🐰 An image rebrand, so clean and neat,
From gitlab halls to nvidia's street,
The workers hop with fresh new threads,
Runtime refreshed, now properly fed! 🎉

Pre-merge checks

❌ Failed checks (2 warnings, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description follows the required template structure with all four sections present (Overview, Details, Where should the reviewer start?, and Related Issues), but all sections contain only placeholder text or comments from the template itself rather than actual content. The Overview and Details sections contain HTML comment placeholders prompting for information, the "Where should the reviewer start?" section is empty, and the Related Issues section only lists the placeholder "closes GitHub issue: #xxx". No substantive information about the changes, rationale, or affected files has been provided by the author.	All template placeholder sections must be filled with actual content. The author should provide a clear overview of why the container image references are being updated, explain the details of the change (which images, why the new registry, what the new tag represents), identify the specific file (components/backends/vllm/deploy/agg.yaml) for reviewer focus, and reference the related GitHub issue number instead of the placeholder "#xxx".
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Title Check	❓ Inconclusive	The PR title "fix: accidental overwrite" is vague and lacks specificity about the actual changes made. While the raw summary indicates the main change is updating container image references in components/backends/vllm/deploy/agg.yaml from one registry to another, the title does not communicate this concrete detail. Instead, it uses generic phrasing ("accidental overwrite") that doesn't convey meaningful information about what was changed, making it difficult for someone scanning the history to quickly understand the purpose of this PR. The title suggests a fix was made but leaves the actual subject unclear.	Consider revising the title to be more specific and descriptive of the actual change, such as "fix: update vllm container image references in agg.yaml" or similar phrasing that clearly indicates what was updated and where. This would make the PR more understandable when reviewing commit history and better convey the intent of the changeset to reviewers and future maintainers.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}