Volumes and snapshots¶
VirtFoundry storage has volumes (persistent disks) and two different snapshot types.
Volumes¶
PVC-backed disks in the tenant namespace (default StorageClass from Helm platform.storage.defaultClass).
UI: Storage → Volumes (/volumes) — create / delete.
| Method | Path |
|---|---|
| GET | /api/v1/volumes |
| POST | /api/v1/volumes |
| DELETE | /api/v1/volumes/{id} |
Attach volumes to a running or stopped VM from the VM detail page — see Virtual machines.
StorageClass
Use Longhorn (or another CSI with snapshots) beyond throwaway labs. local-path is fine for a first VM, not for volume snapshots. See Configuration.
Two snapshot features¶
| Kind | UI / API | Kubernetes API | Cluster need |
|---|---|---|---|
| VM snapshot | /vm-snapshots, VM detail |
VirtualMachineSnapshot |
KubeVirt (already required) |
| Volume snapshot | /snapshots |
VolumeSnapshot |
CSI snapshotter + snapshot-capable SC |
VM snapshots¶
Point-in-time snapshot of a whole guest (KubeVirt).
| Action | API |
|---|---|
| List / create | GET/POST /api/v1/vm-snapshots |
| Delete | POST /api/v1/vm-snapshots/delete |
| Restore | POST /api/v1/vm-snapshots/restore |
Works on lab StorageClasses where volume snapshots do not.
Volume snapshots¶
CSI snapshot of a PVC.
| Action | API |
|---|---|
| List / create | GET/POST /api/v1/snapshots |
| Delete | Not exposed yet |
Set platform.storage.snapshotClass (e.g. longhorn) or rely on a default VolumeSnapshotClass. Details and prerequisites: Configuration — Snapshots.
local-path
Volume snapshots fail without CSI external-snapshotter + a capable driver. Use VM snapshots on pure local-path labs.