NVIDIA / NVIDIA/nvcf

Validate native shared storage and document rollout

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

Validate SMB fallback, native Secret projection, RBAC, Secret updates, metadata updates, projected-file latency, encryption-at-rest evidence handling, and cold-start metrics. Also validate a fully SMB-free configuration using native Secrets with an RWX PVC shared-data backend.

Document canary promotion, value pinning, rollback settings, go/no-go checks, and SMB CSI lifecycle considerations.

Definition of Done

  • End-to-end tests verify the expected sensitive-data files and updates.
  • Fully SMB-free mode leaves no NVCF-managed SMB server or SMB CSI PVC.
  • The rollout guide includes rollback to either SMB backend.
  • Validation evidence and known limitations are recorded without private environment details.

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.