Storage

Manage persistent volumes, snapshots, and recovery as separate concerns.

Choose a storage class#

Use block volumes for databases and stateful workloads, and object buckets for application assets or exports. A volume belongs to one region; attaching it in another region requires a deliberate restore or migration.

Class	Access pattern	Recovery option
standard-block	General-purpose read/write	Scheduled snapshots
fast-block	Latency-sensitive workloads	Scheduled snapshots
object	Objects addressed by key	Version retention

Declare a persistent volume#

apiVersion: universe/v1
kind: Volume
metadata:
  name: catalog-data
spec:
  class: standard-block
  capacityGiB: 100
  retentionPolicy: retain
  snapshotPolicy:
    schedule: daily
    keep: 14

Practice a restore#

Restore snapshots into a new volume, attach it to an isolated validation service, and verify application integrity before switching production traffic. A snapshot is a recovery point, not proof that a database is application-consistent.