Record state hub IDs for railiance deployment

This commit is contained in:
2026-05-22 13:51:51 +02:00
parent e2aac3ad8c
commit f4c38e2d5f

View File

@@ -9,6 +9,7 @@ owner: codex
topic_slug: custodian
created: "2026-05-22"
updated: "2026-05-22"
state_hub_workstream_id: "5b1e98a0-1d5d-41bd-a44e-c82502b5a60d"
---
# ACTIVITY-WP-0005 - Railiance01 Production Service
@@ -19,6 +20,7 @@ updated: "2026-05-22"
id: ACTIVITY-WP-0005-T01
status: done
priority: high
state_hub_task_id: "0247ebd0-7f94-41d1-8439-abfa21e4466d"
```
Confirm railiance01 access, operating system, container runtime, and cluster
@@ -30,6 +32,7 @@ shape before selecting the production deployment path.
id: ACTIVITY-WP-0005-T02
status: done
priority: high
state_hub_task_id: "5689510b-c41f-46c9-844e-6f619473e50d"
```
Create a K3s-native deployment bundle for activity-core, including infrastructure,
@@ -41,6 +44,7 @@ runtime jobs, API, worker, event router, and generated Kubernetes secrets.
id: ACTIVITY-WP-0005-T03
status: done
priority: high
state_hub_task_id: "605ca0bf-733b-41c0-ad36-d3c3560f77cf"
```
Build the production image locally, transfer it to railiance01, and import it
@@ -52,6 +56,7 @@ into the K3s containerd image store.
id: ACTIVITY-WP-0005-T04
status: done
priority: high
state_hub_task_id: "66bbc149-6d81-48e5-8f0e-7909353dc22c"
```
Apply the manifests on railiance01, run migrations and sync jobs, then verify