fix: deploy safe postgres credential diagnostics #69
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!69
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/20ca7f9d-postgres-logging"
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
Deploy postgres-operator #2, which removes credential SQL and raw driver errors from operator diagnostics. Morten approved publication and deployment.
Evidence
After: actual operator uses published 0.0.20 image index
sha256:4a1f2b026b92c3f322b14b987cc69ab0395a986efa5031702c1d61eb3db785c8, one ready replica/zero restarts; all 15 databases Ready and same PVC Bound.5988cf3; downloaded core 0.1.9 pins postgres 0.0.20.5988cf3and postgres 0.0.20 Synced/Healthy. Current operator log/status scan has zero credential SQL. Synthetic tests prove failure paths; no production failure injection. Final task health check HEALTHY, 82/82 Applications Synced/Healthy.Merge danger
Door: one-way
Published Helm artifacts persist. Deployment pin is reversible. Publication/deployment explicitly approved.
Blast radius: app
One operator rollout; no credential, schema, PVC, permission or resource-limit change. Separate server-log exposure remains HIGH in HOMEIT-433.
Rollback and verification
51d8f6144d393c85bc6d393c85bc6d5988cf3b75WIP: fix: deploy safe postgres credential diagnosticsto fix: deploy safe postgres credential diagnostics