Apply shared-storage mounts to MiniService workloads
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
Replace annotation-only storage handling with deterministic MiniService pod-spec mutation before workloads are applied. Build a typed mount plan from StorageRequest.Status.SharedStorage after storage is ready. Apply the plan to Pods and pod templates in Deployments, ReplicaSets, StatefulSets, Jobs, and CronJobs, including every workload container and init container.
The utility workload should receive its HCL ConfigMap, ESS_HCL_SOURCE, and writer ServiceAccount without mounting the workload's read-only sensitive-data Secrets into the writer path.
Definition of Done
- Tests cover every supported workload kind, container, and init container.
- Reserved-volume replacement, SMB fallback, native Secret mounts, and utility-workload mutation are covered.
- Existing paths remain
/var/secrets,/var/run/nvcf/info, and/var/task. - MiniService storage no longer depends on legacy storage annotations.
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.