fix(cloud-tasks): pin the chart to an image tag that exists

[balajinvda]

Why

The self-managed stack publish lane in nvcf-internal has failed repeatedly with:

Could not resolve 1 artifact(s) under nvcr.io/<ns>/ncp-dev:
nvct-service-oss:1.64.1  failed to request manifest head ... not found [http 404]

The chart pinned appVersion and image tag 1.64.1. That tag does not exist under nvct-service-oss and never will.

cloud-tasks v1.64.1 was released 2026-08-27. At that point the release config had two image destinations, nvcf-cloud-tasks and kaze. The nvct-service-oss destination the chart reads from was added a week later, on 2026-09-03, so 1.64.1 was published under the old names only.

v1.65.0 was released 2026-09-04, after the destination existed, and its promote job pushed successfully:

nvcr.io/<ns>/ncp-dev/nvct-service-oss:1.65.0: digest: sha256:2d0f394e...c9e6e1

What changed

appVersion and the image tag move together from 1.64.1 to 1.65.0.

Applied with tools/ci/chart-version-bumper, which confirmed the two fields agreed before moving them:

cloud-tasks-helm: 1.64.1 -> 1.65.0 (appVersion and image tag agree)

Customer Release Notes

Not customer visible. Fixes a release pipeline failure.

Plan Summary

Not applicable.

Usage

Not applicable.

Testing

helm lint passes on the chart. The target tag was verified present in ncp-dev by reading the promote job log for the 1.65.0 release rather than assuming it published.

Notes

Skipping 1.64.2 is deliberate: it was released 2026-09-04 at 01:14, still before the 2026-09-03 destination change had a release run through it, and 1.65.0 is the first version confirmed present under nvct-service-oss.

Worth a follow-up: nothing failed when 1.64.1 was published without the destination that the chart reads from. The chart pointed at a repository the release was not writing to, and the only signal was a stack publish failure a week later. The chart-to-service edge added in #1215 plus the bumper in #1222 close the version-drift half of this; the destination-versus-chart mismatch is a separate gap.

References

None

Related Merge Requests/Pull Requests

None

Dependencies

None

Github commit:
fix(cloud-tasks): pin the chart to an image tag that exists

Co-authored-by: Balaji Ganesan bganesan@nvidia.com

Summary by CodeRabbit

• Chores
  • Updated the nvct-api application and container image to version 1.65.0.
  • Ensures deployments use the latest release version.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 21b88055-8615-49ee-925e-217175c15e78

📥 Commits

Reviewing files that changed from the base of the PR and between cea4024 and 1b1a81d.

📒 Files selected for processing (2)

• deploy/helm/cloud-tasks/nvct-api/Chart.yaml
• deploy/helm/cloud-tasks/nvct-api/values.yaml

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

📝 Walkthrough

Walkthrough

The Helm chart application version and the nvct-api container image tag were updated from 1.64.1 to 1.65.0.

Changes

nvct-api release configuration

Layer / File(s)	Summary
Align chart and image versions deploy/helm/cloud-tasks/nvct-api/Chart.yaml, deploy/helm/cloud-tasks/nvct-api/values.yaml	The chart appVersion and nvct-api image tag now use 1.65.0.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 1b1a8

This updates the nvct-api chart and deployed image version to 1.65.0. The chart and image tag remain aligned, with no identified merge-blocking risk.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title uses valid Conventional Commits syntax with the required scope. The fix type accurately describes updating the chart to an image tag that exists.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/cloud-tasks-chart-1650

---

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