NVIDIA / NVIDIA/nvcf

Shared Storage V2: Write rendered data to Kubernetes Secrets

Open
#144 0 comments 0 reactions 1 assignee View on GitHub

@shobham-nv is already working on this.

Since Jul 15, 2026.

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

Description

Description

Add an ESS Agent template sink that writes rendered sensitive data to a configured key in an existing Kubernetes Secret instead of a filesystem destination.

Requirements

  • Parse k8s_secret { name namespace key }.
  • Reject templates that set both destination and k8s_secret.
  • Use the in-cluster Kubernetes client to patch only the owned data[key].
  • Enforce the 768 KiB decoded per-key and 900 KiB decoded total-data limits.
  • Preserve unchanged-value no-op behavior and return clear errors for NotFound, Forbidden, and retryable API failures.

Definition of Done

  • Tests cover configuration validation, patch behavior, unchanged values, size limits, and API errors.
  • Unrelated Secret keys remain unchanged.

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.