Skip to content

fix(helm): align 26.08-RC1 defaults with Test Plan image matrix - #2531

Open
jdye64 wants to merge 4 commits into
NVIDIA:mainfrom
jdye64:fix/helm-26.08-rc1-image-matrix
Open

fix(helm): align 26.08-RC1 defaults with Test Plan image matrix#2531
jdye64 wants to merge 4 commits into
NVIDIA:mainfrom
jdye64:fix/helm-26.08-rc1-image-matrix

Conversation

@jdye64

@jdye64 jdye64 commented Aug 17, 2026

Copy link
Copy Markdown
Collaborator

Description

Align the published 26.08-RC1 Helm chart defaults with the release Test Plan service and NIM image matrix so a default install no longer ships unqualified 26.5.0 / stale Parse, Omni, or Answer LLM tags.

  • Pin chart version/appVersion and service.image to nvcr.io/nvstaging/nim/nrl-service:26.08-RC1
  • Update optional NIM defaults: Omni 2.0.4-variant, Nemotron Parse v2.0:2.0.8-variant, Answer LLM Super-49B v1:1.10.1
  • Align Helm README, OpenShift examples, support matrix, release notes, troubleshoot, multimodal Parse guidance, self-hosted Parse remote model default, and regression tests

Checklist

  • I am familiar with the Contributing Guidelines.
  • New or existing tests cover these changes.
  • The documentation is up to date with these changes.

Pin the chart service and optional NIM defaults to the release-approved
artifact matrix so default installs no longer ship unqualified 26.5.0 /
stale Parse/Omni/Answer LLM tags.
@jdye64
jdye64 requested review from a team as code owners August 17, 2026 21:02
@jdye64
jdye64 requested a review from edknv August 17, 2026 21:02
@copy-pr-bot

copy-pr-bot Bot commented Aug 17, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

Update release notes, support matrix, troubleshoot, multimodal Parse
guidance, and OpenShift install examples to match the Test Plan pins.
@jdye64
jdye64 marked this pull request as draft August 17, 2026 21:06
@greptile-apps

greptile-apps Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

The PR aligns the Helm chart and documentation with the 26.08-RC1 service and optional NIM image matrix.

  • Pins the chart metadata and service image to 26.08-RC1.
  • Updates Parse, Omni caption, and Answer LLM image/model defaults.
  • Synchronizes service configuration, documentation, OpenShift examples, and Helm regression tests.

Confidence Score: 4/5

The PR is not safe to merge until the chart version is changed to valid SemVer so Helm release linting can complete.

The previously reported chart-version defect remains at the current HEAD, and release workflows lint the source Chart.yaml before any packaging-time version rewrite.

Files Needing Attention: nemo_retriever/helm/Chart.yaml

Important Files Changed

Filename Overview
nemo_retriever/helm/Chart.yaml Updates chart metadata to 26.08-RC1, but the chart version retains the previously reported invalid leading-zero SemVer component.
nemo_retriever/helm/values.yaml Aligns the service, Parse, Omni caption, and Answer LLM defaults with the release image matrix.
nemo_retriever/src/nemo_retriever/operators/extract/parse/nemotron_parse.py Updates the default self-hosted Nemotron Parse model selection for the v2.0 deployment.
nemo_retriever/src/nemo_retriever/service/config.py Aligns the service-side Nemotron Parse model default with the updated Helm deployment.
nemo_retriever/helm/README.md Documents the updated release image and optional NIM defaults.
nemo_retriever/helm/openshift.md Updates OpenShift deployment guidance and examples for the release image matrix.

Reviews (4): Last reviewed commit: "test: pin Parse contract tests to explic..." | Re-trigger Greptile

type: application
version: "26.5.0"
appVersion: "26.5.0"
version: "26.08-RC1"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P1 Invalid Helm chart version

When the release workflows run helm lint, the version value 26.08-RC1 is rejected because SemVer numeric identifiers cannot contain leading zeros, blocking chart packaging and publication.

Knowledge Base Used: Repo Overview and Deployment

Prompt To Fix With AI
This is a comment left during a code review.
Path: nemo_retriever/helm/Chart.yaml
Line: 21

Comment:
**Invalid Helm chart version**

When the release workflows run `helm lint`, the `version` value `26.08-RC1` is rejected because SemVer numeric identifiers cannot contain leading zeros, blocking chart packaging and publication.

**Knowledge Base Used:** [Repo Overview and Deployment](https://app.greptile.com/nvidia-public-github/-/custom-context/knowledge-base/nvidia/nemo-retriever/-/docs/repo-overview-and-deployment.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

@jdye64
jdye64 marked this pull request as ready for review August 17, 2026 21:10

@jperez999 jperez999 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

NRL Service:
nvcr.io/nvstaging/nim/nrl-service:26.08-RC4

VL Embed:
llama-nemotron-embed-vl-1b-v2:2.3.0

Object Detection:
nemotron-object-detection:2.0.1

OCR:
nemotron-ocr-v2:2.0.1

Parakeet:
parakeet-1-1b-ctc-en-us:1.5.0

Omni:
nemotron-3-nano-omni-30b-a3b-reasoning:2.0.4-variant

VL Reranker:
llama-nemotron-rerank-vl-1b-v2:2.3.0

Nemotron Parse:
nemotron-parse-v1.2:1.7.0-variant

Answer LLM:
llama-3.3-nemotron-super-49b-v1.5:2.0.5

jdye64 added 2 commits August 17, 2026 20:12
Resolve conflicts by keeping the 26.08 Test Plan image matrix while
adopting upstream Parse v1.2/v2.0 contract wiring and docs.
The chart and library now default self-hosted Nemotron Parse chat endpoints
to v2.0, so the no-model case resolves to the v2.0 decoding options instead
of the v1.2 ones. Make the v1.2 protocol test select v1.2 explicitly and add
coverage that the default resolves to the v2.0 contract.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants