Finish architecture-cleanup RAILIANCE-WP-0016 T05
Item 13 is the restore RESOURCE-WP-0002 already proved. Item 14 retires the dead Bitnami postgresql-ha deploy path and gates Valkey until a consumer exists. Item 17 publishes the versioned S3 consumer-interface index.
This commit is contained in:
parent
2af19627e1
commit
1eb5fa51ed
8 changed files with 156 additions and 69 deletions
|
|
@ -1,9 +1,16 @@
|
|||
# PostgreSQL HA — Platform Service
|
||||
# PostgreSQL HA — retired
|
||||
|
||||
**Chart:** `bitnami/postgresql-ha`
|
||||
**Namespace:** `platform`
|
||||
**Managed by:** `railiance-platform` (S3)
|
||||
**Workplan:** `RAIL-PL-WP-0001`
|
||||
**Status:** retired 2026-08-15 (`RAILIANCE-WP-0016` item 14)
|
||||
**Superseded by:** CloudNativePG clusters in `databases` (`apps-pg`,
|
||||
`forgejo-db`, `platform-pg`, and the other CNPG instances).
|
||||
**Do not deploy.** `make pg-deploy` is fail-closed.
|
||||
|
||||
The Bitnami `postgresql-ha` (repmgr + pgpool) stack never ran as a live
|
||||
S3 service on railiance01. There is no `platform` namespace and no
|
||||
matching pods. Gitea’s historical subchart in S2 was replaced by
|
||||
`forgejo-db`. Keep this file as the retirement record and the
|
||||
pgpool-password incident note. New databases go through `docs/apps-pg.md`
|
||||
or `rapp-postgres`.
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue