NVIDIA / NVIDIA/nvcf

Provision native Kubernetes resources for shared-storage secrets

Open
#148 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

Have NVCA manage the Kubernetes resources used to deliver per-function sensitive data: runtime and metadata Secrets, the utility ServiceAccount and RBAC, an HCL ConfigMap, and an optional NetworkPolicy. Limit the writer Role to get and patch on the two named Secrets through resourceNames. Render the secret references into the per-function HCL configuration and attach the resources to the StorageRequest ownership lifecycle.

Definition of Done

  • Creation, update, idempotency, owner references, and cleanup are covered by tests.
  • RBAC grants only the required verbs on the named Secrets.
  • Runtime data remains available at /var/secrets/secrets.json and metadata at /var/run/nvcf/info/self.
  • Native resources are not created when secretBackend=smb or shared-storage configuration is omitted.

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.