NVIDIA / NVIDIA/nvcf

release: migration tasks report their own completion status

Open
#1,978 0 comments 0 reactions 1 assignee View on GitHub

@kristinapathak is already working on this.

Since Sep 18, 2026.

ci
Dominant language
Go
Stars
218
Forks
72
Avg merge
1d 12h
Merged PRs (30d)
427

Description

A post-install hook Job runs once and exits, so it cannot come back hours later to mark an asynchronous backfill complete. Either it blocks until the backfill finishes — which defeats the point of the backfill being asynchronous — or the status is never updated and the receipt is permanently wrong.

The task that runs the migration is the thing that knows when it is done, is already running in-cluster, and already has to exist. It should write its own status into the receipt. The receipt writer then only has to record installed version and bundle digest at install time, and nothing has to watch anything.

Getting completion reported honestly is the part of this design that is not solved for us anywhere and deserves the most care. A receipt must never claim readiness merely because Helm finished.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.