fix(helm): keep remote consumers off artifact PVCs
What type of PR is this?
- bug
- cleanup
- documentation
- enhancement
- api change
What this PR does / why we need it:
A Liqo consumer can bind its workload artifact PVC to a provider virtual node. The Snapshot operator currently mounts that claim too, preventing it from remaining on the consumer cluster.
Add operator.mountArtifactPVC, defaulting to true. Remote-only consumers can disable the mount and use a bounded scratch directory while provider agents retain artifact access. Disabling the mount requires consumer provenance, remote cleanup delegation and a disabled local agent.
Which issue(s) this PR fixes:
No issue linked yet. The fork has issues disabled; keep this PR in draft until the issue-reference requirement is resolved.
How was this tested?
- All 92 Helm unit tests pass.
- Helm lint passes.
- Default rendered resources match the base chart.
- Consumer and provider values from the internal chart render successfully with the updated Snapshot chart.
Live GPU capture and restore were not tested.
Special notes for your reviewer:
Native and mixed installations retain the existing PVC mount. Clusters with existing native Snapshot content must also retain it.
This fixes a prerequisite for doublewordai/internal#4904. It adds an optional Helm value without changing CRD or Go APIs.
Does this PR introduce an API change?
NONE
Additional documentation, e.g. enhancement proposals, usage docs:
docs/operations/liqo-control-plane.md
Checklist
- Commits are signed off (git commit -s), per CONTRIBUTING.md (../CONTRIBUTING.md)
- make check test passes locally
- Documentation is updated where behavior changed