CRD reference¶
Per-CRD, per-field reference for the eight CRDs in
kopiur.home-operations.com/v1alpha1. Each page explains, field by field, what a
field does, its default, the allowed values, and when you'd set it — the detail
that used to live in the CRD description text.
Three layers, by how much detail you want:
- Field reference — the terse, exhaustive table of every field's type/default/immutability across all CRDs. Start here to look up a single field fast.
- These pages — the same fields with the fuller per-field explanation (defaults, allowed values, gotchas, how a field maps to a kopia behavior).
- Task guides (Backups, Restores, Repositories, …) — narrative how-to that ties fields together for a goal.
The design rationale behind why these fields are shaped the way they are (sub-objects, materialized defaults, CEL cost budgets, immutability rules) lives in CRD design rationale for contributors.
The CRDs¶
- Repository — a namespaced kopia repository.
- ClusterRepository — a cluster-scoped, multi-tenant repository.
- SnapshotPolicy — the backup recipe (what to back up).
- Snapshot — one backup invocation.
- SnapshotSchedule — the cron that fires snapshots.
- Restore — restore data from a repository.
- Maintenance — repository maintenance (quick/full).
- RepositoryReplication — off-site mirror.
- Shared sub-objects — types reused across CRDs (Backend, MoverSpec, …).