coulomb/railiance-apps
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

RAILIANCE-WP-0002 T04: link to platform RAILIANCE-WP-0003

Browse Source 
apps-pg cluster now has a draft workplan in railiance-platform
(RAILIANCE-WP-0003, workstream 665b3b9b). Adds the consumer recipe
inline so this workplan is self-contained once the platform cluster
goes healthy.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
Bernd Worsch
2026-05-19 00:51:06 +02:00
parent 94c02f9608
commit 84271973ae
1 changed files with 14 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
workplans/railiance-apps-WP-0002-vergabe-teilnahme-on-railiance01.md
View File

@@ -327,9 +327,20 @@ new shared `apps-pg` cnpg cluster being provisioned by `railiance-platform`
(per resolved decision D-01). (per resolved decision D-01).
Blocked on: `apps-pg` cluster reaching `Cluster in healthy state` in Blocked on: `apps-pg` cluster reaching `Cluster in healthy state` in
namespace `databases`. Coordination message sent to `railiance-platform` namespace `databases`. Tracked by `railiance-platform`
on 2026-05-18; record the platform workstream/task IDs here once **`RAILIANCE-WP-0003`** (workstream
returned. `665b3b9b-608a-4be4-84b6-dcb8261ff57b`), proposed 2026-05-19 in
response to the coordination thread.
Consumer recipe (from RAILIANCE-WP-0003 T06):
1. Label the `vergabe-teilnahme` namespace
`railiance.io/postgres-client=apps-pg` so the platform's ingress
NetworkPolicy permits the connection.
2. Create a credential Secret in that namespace for the `vergabe` role.
3. Create a cnpg `Database` CR pointing at cluster `apps-pg` with
`ownerName: vergabe` and the credential Secret.
4. DSN: `postgresql://vergabe:...@apps-pg-rw.databases:5432/vergabe_db`,
wired into the SOPS Helm values in T05.
Approach: Approach: