Automated MariaDB backups for krona #77

New issue

Open

opened 2026-09-10 17:02:07 +00:00 by znibb · 0 comments

znibb commented

2026-09-10 17:02:07 +00:00

Owner

Goal

Set up automated backups for krona-mariadb. There's currently no backup for this database. A pod restart is fine (PVC survives), but PVC loss, corruption, or a bad migration has no recovery path.

Tasks

[ ] Write a mysqldump CronJob manifest for krona-mariadb (kubernetes/apps/krona/mariadb/)
[ ] Store dumps outside the cluster's local storage (S3-compatible target, not the same PVC/node as the database)
[ ] Set a retention policy and prune old dumps
[ ] Test a full restore from a dump and document the steps in a docs/restore.md (or similar)

Notes

No offsite backup pipeline exists in this repo yet. Issue #7 covers the same gap for PostgreSQL; if that CronJob pattern lands first, reuse it here instead of building a second one from scratch.

## Goal Set up automated backups for `krona-mariadb`. There's currently no backup for this database. A pod restart is fine (PVC survives), but PVC loss, corruption, or a bad migration has no recovery path. ## Tasks [ ] Write a `mysqldump` CronJob manifest for `krona-mariadb` (kubernetes/apps/krona/mariadb/) [ ] Store dumps outside the cluster's local storage (S3-compatible target, not the same PVC/node as the database) [ ] Set a retention policy and prune old dumps [ ] Test a full restore from a dump and document the steps in a docs/restore.md (or similar) ## Notes No offsite backup pipeline exists in this repo yet. Issue #7 covers the same gap for PostgreSQL; if that CronJob pattern lands first, reuse it here instead of building a second one from scratch.

znibb referenced this issue

2026-09-25 15:06:26 +00:00

feat: Add Rybbit (open-source web analytics) with HA replicas #107