Expand description
The RepositoryReplication CRD — mirror a repository’s blobs to a second
backend on a schedule (ADR-0005 §13(d)). The one net-new CRD: it is the “2” in
3-2-1 backup, wrapping kopia repository sync-to.
It is namespaced (it lives alongside its source repository, mirroring
Maintenance) and references either a namespaced Repository or a cluster-scoped
ClusterRepository via a RepositoryRef. The controller schedules a per-slot
mover Job (croner + deterministic jitter, single-flight, repo-ready gate,
transition-guarded status) exactly like Maintenance.
Structs§
- Repository
Replication - Auto-generated derived type for RepositoryReplicationSpec via
CustomResource - Repository
Replication Spec - Mirror a source repository’s blobs to a destination backend on a schedule (
kopia repository sync-to). - Repository
Replication Status - Observed state of a
RepositoryReplication. - Sync
Options - Tuning knobs for
kopia repository sync-to(issue #216): copy parallelism, destination pruning, and the blob-sync tri-states/throughput caps kopia exposes on the command. Every field’sNone/falsereproduces kopia’s own default, so an absentsyncblock is exactly today’s behavior. Pure scalars (no k8s-openapi embeds), so this derivesEqunlike its parent spec.
Enums§
- Repository
Replication Phase - Lifecycle phase of a replication.