Inspect persistent volumes — list, get, delete, detach, retry-provision, restore from snapshot. (Volumes are created via `rune cast`.)
rune volume <subcommand> [flags]rune vol <subcommand> [flags] # short alias
A Volume is a namespaced unit of durable storage backed by a driver. See the
storage concept for the lifecycle and how services
consume them via claim / claimTemplate.
Subcommands
Command
Purpose
rune volume list
List volumes in a namespace.
rune volume get <name>
Show one volume's full status.
rune volume delete <name>
Delete the row; reclaim policy decides the rest.
rune volume detach <name>
Clear Bound state so a replacement can attach.
rune volume retry-provision <name>
Re-drive a Failed/Stalled volume back to Pending.
rune volume restore <name>
Provision a new volume from a snapshot.
Examples
# List in current namespacerune volume list# Across all namespacesrune vol list -A# Show onerune volume get pgdata-postgres-0 -n prod -o yaml# Apply from a spec — Volumes are created via `rune cast`, the same# declarative path used for every other resource.rune cast web-data.yaml# Delete (reclaim policy applies — see storage concept)rune volume delete web-data# Volume stuck Bound after the instance vanished — break the bindrune volume detach pgdata-postgres-1 -n prod# Provisioning failed — fix the underlying problem, then re-driverune volume retry-provision pgdata-postgres-1 -n prod# Restore from a snapshot into a new volume rowrune volume restore web-data-restored \ --from-snapshot web-data-2025-11-15 \ --snapshot-namespace prod \ --storage-class local \ -n prod