Note apps-pg live and coulomb-social DB connectivity in playbook
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

Cluster healthy; role/database present; env Secret keys established.
This commit is contained in:
tegwick 2026-08-09 02:18:17 +02:00
parent d8d3d5b1a0
commit 350f66472c

View file

@ -129,7 +129,9 @@ Operator session via `warden access coulomb-social-runtime-env` routing + assemb
| Secret `coulomb-social/coulomb-social-app-credentials` | basic-auth username/password for role |
| Secret `databases/coulomb-social-app-credentials` | same password for future CNPG managed role |
| Catalog `coulomb-social-runtime-env` | active in ops-warden routing |
| apps-pg cluster | **not yet deployed** — DATABASE_URL is assembled; DB/role activate when apps-pg + Database CR are applied |
| apps-pg cluster | **healthy** (2026-08-09) — primary `apps-pg-1` |
| Role `coulomb_social` / DB `coulomb_social_db` | present; CNPG Database CR applied |
| Connectivity smoke | from ns `coulomb-social`: `OK: coulomb_social coulomb_social_db` |
Re-verify key names only:
@ -137,4 +139,5 @@ Re-verify key names only:
warden route show coulomb-social-runtime-env --json
kubectl -n coulomb-social get secret coulomb-social-env -o json \
| python3 -c 'import sys,json; print(sorted((json.load(sys.stdin).get("data") or {}).keys()))'
kubectl get cluster apps-pg -n databases -o wide
```