Provision native Kubernetes resources for shared-storage secrets
Open
@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.jsonand metadata at/var/run/nvcf/info/self. - Native resources are not created when
secretBackend=smbor shared-storage configuration is omitted.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.