coulomb/railiance-platform
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Finish architecture-cleanup RAILIANCE-WP-0016 T05
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Has been cancelled
Details

Browse source 
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:
codex 2026-08-15 14:43:44 +02:00
parent 2af19627e1
commit 1eb5fa51ed
8 changed files with 156 additions and 69 deletions
Download patch file Download diff file Expand all files Collapse all files

16
.claude/rules/stack-and-commands.md
View file

@ -1,18 +1,18 @@
## Stack
- **Language:** Kubernetes manifests + Helm values, Bash Make targets
- **Key deps:** CloudNative-PG (cnpg) clusters, Valkey, OpenBao, SOPS/age; runs against the S2 cluster on railiance01
- **Key deps:** CloudNative-PG (cnpg) clusters, OpenBao, SOPS/age; runs against the S2 cluster on railiance01. Bitnami postgresql-ha is retired. Valkey is declared, not deployed.
## Dev Commands
```bash
make help # list all targets (db-*, apps-pg-*, pg-*, valkey-*, openbao-*)
make db-status # gitea-db cnpg cluster health (read-only)
make help # list all targets (db-*, apps-pg-*, openbao-*)
make db-status # gitea-db / forgejo-db cnpg cluster health (read-only)
make apps-pg-status # shared apps-pg cluster health (read-only)
make pg-status # standalone PostgreSQL HA pod status (read-only)
make valkey-status # Valkey pod status (read-only)
make db-deploy | apps-pg-deploy | pg-deploy | valkey-deploy # production-touching
make pg-status # confirms retired Bitnami postgresql-ha is absent
make valkey-status # confirms Valkey is absent
make db-deploy | apps-pg-deploy # production-touching
```
`*-deploy` targets change production platform services — operator approval
required. `*-status` / `*-logs` targets are read-only and safe.
`pg-deploy` and `valkey-deploy` are fail-closed. `*-status` / `*-logs`
targets are read-only and safe.