feat: manage backup retention in Klio instead of Kopia - #238

Open

gabriele-wolfox wants to merge 23 commits into

mainfrom

dev/168

Commits on Sep 15, 2026

feat: manage backup retention in Klio instead of Kopia

gabriele-wolfox
authored and
fcanovai
committed
9b6a9e8
feat(retention): apply retention on demand with a new command

gabriele-wolfox
authored and
fcanovai
committed
97ed586
fix(config): decode the tier1 retention policy from the client config

armru
authored and
fcanovai
committed
02b7cd2
fix(server): disable Kopia's own snapshot retention

armru
authored and
fcanovai
committed
857f5ce
test(retention): cover applyRetention with a fake client

armru
authored and
fcanovai
committed
74d2430
fix(retention): reject an empty or invalid cluster name in ApplyRetention

armru
authored and
fcanovai
committed
6dbfbf5
fix(retention): retry a maintenance-only task when tier1 maintenance fails

armru
authored and
fcanovai
committed
5f1458c
fix(queue): do not purge the backup dead-letter queue on maintenance tasks

armru
authored and
fcanovai
committed
ef3fa6e
fix(backup): delete the metadata snapshot of a backup last

armru
authored and
fcanovai
committed
d12368f
fix(operator): treat a pruned retention block as no policy

armru
authored and
fcanovai
committed
90b0712
test(e2e): list only the cluster's backups in the tier2 retention feature

armru
authored and
fcanovai
committed
57464a8
chore(retention): drop leftovers of the Kopia pin based flow

armru
authored and
fcanovai
committed
78ee194
fix(retention): require a complete tier2 copy before tier1 deletes a backup

armru
authored and
fcanovai
committed
945f086
fix(retention): fail the backup listing when a metadata snapshot is unreadable

armru
authored and
fcanovai
committed
f0b48e0
fix(retention): bind ApplyRetention to the client certificate cluster

armru
authored and
fcanovai
committed
d8329bb
fix(retention): do not wait for tier2 on backups that skip the relay

armru
authored and
fcanovai
committed
266c455
docs(retention): document backup ordering and the tier2 guard

armru
authored and
fcanovai
committed
c047590
test(retention): verify tier1 retention and share the flow with tier2

gabriele-wolfox
authored and
fcanovai
committed
6fb8741
test(e2e): count only the cluster's backups in the retention checks

armru
authored and
fcanovai
committed
8804974
test(e2e): verify the tier1 WAL horizon follows base retention

armru
authored and
fcanovai
committed
95838a5
fix(retention): let tier1 delete backups that tier2 retention already removed

armru
authored and
fcanovai
committed
6330c33
fix(operator): make the retention latest field optional in the CRD

armru
authored and
fcanovai
committed
d937a3f
docs(agents): list the retention config files among the synced pairs

armru
authored and
fcanovai
committed
82f05d1

Navigation Menu

Uh oh!

feat: manage backup retention in Klio instead of Kopia - #238

feat: manage backup retention in Klio instead of Kopia#238
gabriele-wolfox wants to merge 23 commits into
mainfrom
dev/168

Commits on Sep 15, 2026

feat: manage backup retention in Klio instead of Kopia

feat(retention): apply retention on demand with a new command

fix(config): decode the tier1 retention policy from the client config

fix(server): disable Kopia's own snapshot retention

test(retention): cover applyRetention with a fake client

fix(retention): reject an empty or invalid cluster name in ApplyRetention

fix(retention): retry a maintenance-only task when tier1 maintenance fails

fix(queue): do not purge the backup dead-letter queue on maintenance tasks

fix(backup): delete the metadata snapshot of a backup last

fix(operator): treat a pruned retention block as no policy

test(e2e): list only the cluster's backups in the tier2 retention feature

chore(retention): drop leftovers of the Kopia pin based flow

fix(retention): require a complete tier2 copy before tier1 deletes a backup

fix(retention): fail the backup listing when a metadata snapshot is unreadable

fix(retention): bind ApplyRetention to the client certificate cluster

fix(retention): do not wait for tier2 on backups that skip the relay

docs(retention): document backup ordering and the tier2 guard

test(retention): verify tier1 retention and share the flow with tier2

test(e2e): count only the cluster's backups in the retention checks

test(e2e): verify the tier1 WAL horizon follows base retention

fix(retention): let tier1 delete backups that tier2 retention already removed

fix(operator): make the retention latest field optional in the CRD

docs(agents): list the retention config files among the synced pairs