Critical: Migrate mcd-tracker Postgres to CNPG shared cluster #189
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/pal-e-platform#189
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
Bug
Lineage
standalone — discovered scope from #187 review. Same vulnerability as basketball-api.
Repo
forgejo_admin/pal-e-platformWhat Broke
mcd-tracker Postgres is a standalone Deployment pod with local-path PVC, zero backups, zero replication — identical to the basketball-api vulnerability documented in #187. Same fix: migrate to CNPG shared cluster.
Repro Steps
kubectl get pvc -n mcd-tracker— standalone postgres-data PVCkubectl get backups -n mcd-tracker— no resources foundExpected Behavior
mcd-tracker database on CNPG with daily Barman backups, WAL archiving, restore verification.
Environment
Acceptance Criteria
Related
#187— basketball-api migration (do first, pattern established)project-mcd-tracker