Replace single daily schedule (240h TTL) with three tiered schedules: - daily-backup: 02:00 nightly, 192h TTL → keeps last 7 daily backups - weekly-backup: 03:00 Sundays, 1032h TTL → keeps last 6 weekly backups - monthly-backup: 04:00 on 1st, 4392h TTL → keeps last 6 monthly backups Kopia handles incremental deduplication at the block level automatically, so each Velero backup only stores changed data despite being a full logical snapshot. No additional incremental configuration required. Update README with retention policy table and updated backup commands. |
||
|---|---|---|
| .git-crypt | ||
| bootstrap | ||
| fritzbox | ||
| k8s | ||
| monitoring | ||
| terraform | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| AGENTS.md | ||
| README.md | ||
README.md
Infrapuzzle
Infrapuzzle is the newly restructured way of implementing my private infrastructure. Currently the following things are in project scope:
- single node k8s "cluster" implemented with kubespray
- development with Vagrant
- host directory storage
- Ingress via host network
terraform
Documentation in subfolder. It takes care of setting DNS records on OVH nameservers.
bootstrap
Documentation in subfolder. It takes care of setting up the k8s cluster itself, including a vagrant dev environment.
k8s
Documentation in subfolder. The services themselfes.