fix: deploy bounded postgres ownership reconciliation #66
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
homelab/core!66
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/3f88f077-postgres-rollout"
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?
Summary
Pin postgres-operator 0.0.19 to deploy conditional ownership repair with bounded lock waits. Publish homelab-core chart 0.1.6. This is rollout phase 1; Authentik stays on 0.1.0 until this operator is verified.
Depends on postgres-operator #1 publishing approved 0.0.19 artifacts. Do not merge before the artifacts exist and Morten approves the core chart publication. The following Authentik rollout is a separate phase so it cannot race the database operator replacement.
Evidence
Merge danger
Door: one-way publication. Main automatically packages and republishes the Helm repository, including new homelab-core 0.1.6. Release approval is required. ArgoCD also reconciles the Git change immediately.
Blast radius: household. Every managed PostgresDatabase is reconciled. Read-only preflight found 17 existing type-owner mismatches outside Authentik; they will be repaired under the existing ownership policy. Data and database server images are unchanged.
Rollback and verification
WIP: fix: deploy bounded postgres ownership reconciliationto fix: deploy bounded postgres ownership reconciliation