Viktor Barzin 9501da81a0 dbaas: document postgresql-backup startingDeadlineSeconds rationale ... Inline note on why the four backup CronJobs moved 10s->600s (bda1bdcb): a 10s deadline silently dropped the 2026-06-13 midnight full-backup run, firing PostgreSQLBackupStale. bda1bdcb rode in the same push as a forgejo change that failed CI on a namespace-quota error, so that pipeline failed before the dbaas apply took effect (live deadline was still 10s). This dbaas-only commit re-triggers the dbaas apply at a clean master so the 600s deadline actually goes live. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-06-13 14:22:24 +00:00
..
postgres	fix: restore tree dropped by 6d224861; land stem95su gdrive-sync (10m) [ci skip]	2026-06-09 08:45:33 +00:00
chart_values.tpl	fix: restore tree dropped by 6d224861; land stem95su gdrive-sync (10m) [ci skip]	2026-06-09 08:45:33 +00:00
cluster.yaml	fix: restore tree dropped by 6d224861; land stem95su gdrive-sync (10m) [ci skip]	2026-06-09 08:45:33 +00:00
main.tf	dbaas: document postgresql-backup startingDeadlineSeconds rationale	2026-06-13 14:22:24 +00:00
mysql_chart_values.yaml	fix: restore tree dropped by 6d224861; land stem95su gdrive-sync (10m) [ci skip]	2026-06-09 08:45:33 +00:00
versions.tf	fix: restore tree dropped by 6d224861; land stem95su gdrive-sync (10m) [ci skip]	2026-06-09 08:45:33 +00:00