NVIDIA / NVIDIA/nvcf

fix(worker-init): restore ESS configuration in released images

Open
#404 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description

Track the ordered delivery of a fix for secret-bearing function deployments.

The worker-init OCI image contains the worker-init binary but does not contain
the ESS configuration files that the binary reads from /etc/ess. When a
function has secrets, worker-init enters the ESS setup path and cannot prepare
the shared ESS configuration. Functions without secrets are unaffected.

This tracking issue covers the source fix, image release, chart consumption,
stack consumption, and end-to-end validation. Each phase depends on the
published artifact from the preceding phase.

Ordered phases

  • #406 - Phase 1: Package ESS configuration in the worker-init OCI image and publish a fixed worker-init release.
  • #408 - Phase 2: Update and publish the API chart with the fixed worker-init image.
  • #407 - Phase 3: Consume the minimal API chart patch on the 0.6 release line.
  • #405 - Phase 4: Consume the API chart on the main stack line and validate secret-bearing deployments.

Definition of Done

  • The worker-init image contains:
    • /etc/ess/config.hcl
    • /etc/ess/secrets.tmpl
    • /etc/ess/accounts-secrets.tmpl
  • An automated test fails if any required ESS image file is absent.
  • The API chart references the fixed worker-init image.
  • Both the 0.6 release line and main stack line reference the fixed API chart.
  • A secret-bearing container function and Helm-chart function both deploy and
    reach an active state.
  • Existing secrets-less deployment coverage continues to pass.

Resources

  • Worker-init source: src/compute-plane-services/worker-init
  • Main stack declaration: deploy/stacks/self-managed/helmfile.d/02-core.yaml.gotmpl

By submitting this issue, you acknowledge that you are an assigned member of the
NVCF development team and agree
to follow our code of conduct and our
contributing guidelines.

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.

Research direction

Start with the ordered phase issues #408, #407, and #405, then inspect src/compute-plane-services/worker-init and deploy/stacks/self-managed/helmfile.d/02-core.yaml.gotmpl. Verify the published worker-init image, chart references, release-line consumption, and deployment validation against the Definition of Done.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, helm, kubernetes
Domain
cloud, devops, infrastructure
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.