Skip to content

Conversation

@athreesh
Copy link
Contributor

@athreesh athreesh commented Aug 12, 2025

super small fix- updated this guide to reflect 0.4.0 and remove API key dependency

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

  • Documentation
    • Updated quickstart to reference release version 0.4.0 in Published Artifacts prerequisites.
    • Removed the NGC authentication step, including API key and repo add instructions.
    • Streamlined setup flow; fetching Helm charts and subsequent steps remain unchanged.
    • Improves clarity and reduces setup steps for a faster, simpler deployment experience.

updated this to reflect 0.4.0 and API key dependency

Signed-off-by: Anish <80174047+athreesh@users.noreply.github.com>
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 12, 2025

Walkthrough

Updates the dynamo_deploy quickstart documentation: increases RELEASE_VERSION from 0.3.2 to 0.4.0 and removes the “Authenticate with NGC” section. Remaining steps, including fetching Helm charts, are unchanged.

Changes

Cohort / File(s) Summary of Changes
Docs: Dynamo Deploy Quickstart
docs/guides/dynamo_deploy/quickstart.md
Bumped RELEASE_VERSION to 0.4.0; removed NGC authentication instructions (API key and helm repo add); retained subsequent Helm chart steps; no API/public interface changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

I twitch my whiskers—version hops to four-oh!
No keys to nibble, no gates to go.
Charts still fetch with a thump and a cheer,
Quickstart’s shorter, the path is clear.
A hop, a skip, deploy we go—
Carrots cached, we’re good to flow. 🥕✨


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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🔭 Outside diff range comments (3)
docs/guides/dynamo_deploy/quickstart.md (3)

88-90: Fix push tag: pushing latest-vllm while tagging $IMAGE_TAG.

You tag the image with $IMAGE_TAG but push latest-vllm. This will fail or push the wrong tag.

Apply:

-docker push <your-registry>/dynamo-base:latest-vllm
+docker push <your-registry>/dynamo-base:$IMAGE_TAG

24-32: Chart URLs publicly accessible; switch to helm pull
Both dynamo-crds-0.4.0.tgz and dynamo-platform-0.4.0.tgz return HTTP 200 without credentials.

Please update the guide to use Helm v3’s modern command:

--- docs/guides/dynamo_deploy/quickstart.md
@@ Fetch Helm Charts
-helm fetch https://helm.ngc.nvidia.com/nvidia/ai-dynamo/charts/dynamo-crds-${RELEASE_VERSION}.tgz
+helm pull https://helm.ngc.nvidia.com/nvidia/ai-dynamo/charts/dynamo-crds-${RELEASE_VERSION}.tgz

-helm fetch https://helm.ngc.nvidia.com/nvidia/ai-dynamo/charts/dynamo-platform-${RELEASE_VERSION}.tgz
+helm pull https://helm.ngc.nvidia.com/nvidia/ai-dynamo/charts/dynamo-platform-${RELEASE_VERSION}.tgz

79-80: Update hard-coded examples to v0.4.0

  • docs/guides/dynamo_deploy/quickstart.md (line 79):
    -export IMAGE_TAG=RELEASE_VERSION # i.e. 0.3.2 - the release you are using
    +export IMAGE_TAG=RELEASE_VERSION # i.e. 0.4.0 - the release you are using
  • examples/deployments/AKS/AKS-deployment.md (line 96):
    -export RELEASE_VERSION=0.3.2
    +export RELEASE_VERSION=0.4.0
  • examples/deployments/EKS/Deploy_Dynamo_Cloud.md (line 19):
    -export IMAGE_TAG=0.3.2.1
    +export IMAGE_TAG=0.4.0.1

Consider sweeping other 0.3.x occurrences in documentation (e.g. components/backends/sglang/README.md:107) to keep examples in sync.

🧹 Nitpick comments (3)
docs/guides/dynamo_deploy/quickstart.md (3)

101-101: Nit: double space and superfluous “the”.

Minor grammar/readability tweak.

Apply:

-The  Nvidia Cloud Operator image will be pulled from the `$DOCKER_SERVER/dynamo-operator:$IMAGE_TAG`.
+The Nvidia Cloud Operator image will be pulled from `$DOCKER_SERVER/dynamo-operator:$IMAGE_TAG`.

107-116: Clarify that image pull secret is optional for public nvcr images.

If 0.4.0 images are public (as implied by removing API key dependency), readers using nvcr.io shouldn’t need a registry secret.

Apply:

-Create the namespace and the docker registry secret.
+Create the namespace and, if your image registry requires authentication, the docker registry secret.
+Note: If you are using the public nvcr.io images for release 0.4.0, you can skip creating the image pull secret.

136-146: Fix mismatched emphasis markers in headings.

Leading/trailing asterisks are inconsistent; renders oddly.

Apply:

-***Step 1: Install Custom Resource Definitions (CRDs)**
+**Step 1: Install Custom Resource Definitions (CRDs)**

-***Step 2: Build Dependencies and Install Platform**
+**Step 2: Build Dependencies and Install Platform**
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 18bb779 and 92755e8.

📒 Files selected for processing (1)
  • docs/guides/dynamo_deploy/quickstart.md (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Build and Test - dynamo
🔇 Additional comments (1)
docs/guides/dynamo_deploy/quickstart.md (1)

15-18: RELEASE_VERSION bump to 0.4.0 looks good.

This aligns with the PR objective and the high-level summary.


```bash
helm repo add nvidia https://helm.ngc.nvidia.com/nvidia --username='$oauthtoken' --password=<YOUR_NGC_CLI_API_KEY>
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Stray markdown code fence breaks rendering.

There’s a lone triple backtick with no matching pair, which will corrupt subsequent markdown blocks.

Apply this diff to remove it:

-```
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
```
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

22-22: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 Prompt for AI Agents
In docs/guides/dynamo_deploy/quickstart.md at line 22 there is a stray triple
backtick that opens a code fence with no matching closing fence; remove that
lone ``` so the markdown rendering is not broken and subsequent blocks render
correctly.

@athreesh athreesh closed this Aug 12, 2025
@athreesh athreesh deleted the athreesh-patch-2 branch August 12, 2025 23:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants