Go to file
Moritz Graf e64aa64c73 velero: implement three-tier backup retention policy
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.
2026-07-01 17:28:11 +02:00
.git-crypt Add 1 git-crypt collaborator 2020-04-05 20:09:08 +02:00
bootstrap I have added a lot of changes from various ai sessions 2026-07-01 11:01:01 +02:00
fritzbox feat(network): implement NAT-free Wireguard site-to-site VPN routing and manual Sonos configuration 2026-05-17 11:42:54 +02:00
k8s velero: implement three-tier backup retention policy 2026-07-01 17:28:11 +02:00
monitoring Adding docs for monitoring in muc 2023-01-16 15:20:26 +01:00
terraform I have added a lot of changes from various ai sessions 2026-07-01 11:01:01 +02:00
.editorconfig Cert-manager deployed 2020-04-05 10:17:47 +02:00
.gitattributes feat(wireguard): setup K8s to FritzBox Site-to-Site VPN 2026-05-17 10:36:06 +02:00
.gitignore Adding monitoring folder to get started 2022-10-09 14:08:07 +02:00
AGENTS.md Adding root level agents file 2026-02-07 09:13:27 +01:00
README.md Refactored README 2026-02-07 11:57:31 +01:00

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.