chore: stagger dev CNPG backup to 03:30 #4

Merged

goern merged 1 commit from refs/pull/4/head into main

2026-07-26 20:32:39 +00:00

goern commented

2026-07-26 20:27:04 +00:00

(Migrated from codeberg.org)

Why

feeldata dev and prod both run their daily CNPG backup at 04:00, so two base backups + WAL archiving hit the shared nostromo-cnpg S3 path at the same instant. This is part of a nostromo-wide effort to spread nightly CNPG backup load (the op1st-emea-b4mad clusters were just staggered too).

What

Move dev to 03:30, leaving prod's timing untouched:

environments/dev/feeldata/postgresql.yaml: 0 0 4 * * * → 0 30 3 * * *

The three feeldata backups are then solo and 30 min apart:

03:00  stage
03:30  dev    ← moved
04:00  prod

Validation

oc apply --dry-run=server accepts the edited ScheduledBackup.

🤖 Generated with Claude Code

## Why feeldata `dev` and `prod` both run their daily CNPG backup at **04:00**, so two base backups + WAL archiving hit the shared `nostromo-cnpg` S3 path at the same instant. This is part of a nostromo-wide effort to spread nightly CNPG backup load (the op1st-emea-b4mad clusters were just staggered too). ## What Move **dev** to **03:30**, leaving prod's timing untouched: - `environments/dev/feeldata/postgresql.yaml`: `0 0 4 * * *` → `0 30 3 * * *` The three feeldata backups are then solo and 30 min apart: ``` 03:00 stage 03:30 dev ← moved 04:00 prod ``` ## Validation `oc apply --dry-run=server` accepts the edited ScheduledBackup. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

b4mad-gitops referenced this pull request from a commit

2026-07-28 19:54:30 +00:00

chore: stagger dev CNPG backup to 03:30 (#4)

No reviewers

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

feeldata/manifests!4

No description provided.

Rows
Columns