feat(statehub): deploy empty railiance state hub

This commit is contained in:
2026-06-25 15:39:53 +02:00
parent ec991f4ccd
commit 8a9bfcc9bd
6 changed files with 39 additions and 15 deletions

View File

@@ -266,8 +266,9 @@ in `deploy/railiance/README.md`.
```task
id: CUST-WP-0011-T05
status: todo
status: done
priority: high
completed: "2026-06-25"
state_hub_task_id: "a307dd46-a8e2-49df-b016-c187759ebcf1"
```
@@ -283,6 +284,19 @@ Checks:
**Done when:** an empty but structurally valid State Hub runs on railiance01.
Completed 2026-06-25: deployed an empty State Hub stack to railiance01.
Created the `state-hub` namespace, generated live-only database and app runtime
Secrets, created the dedicated `state-hub-db` CNPG cluster, and applied database
NetworkPolicies. Fixed the State Hub database egress policy to allow the
in-cluster Kubernetes API service on TCP 443 as well as 6443, which CNPG
needed during initdb. Ran Alembic migrations in a one-shot Kubernetes Job
using image `gitea.coulomb.social/coulomb/state-hub:b536741`; migrations
completed through `e9f0a1b2c3d4 (head)`. Installed the Helm release
`state-hub` into the pre-created namespace with `namespace.create=false`.
Verified Deployment rollout, zero pod restarts, service creation, pod logs,
in-pod Alembic current revision, and `/state/health` via temporary port-forward
returning `{"status":"ok","db":"connected"}`.
---
### T06 — Restore WSL2 data copy into cluster and compare