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

RAIL-BS-WP-0008/0009: operator deploy + admin-sync smoke tooling

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Bernd Worsch
2026-07-02 10:44:06 +02:00
parent 84c005254d
commit 9c55dfb02a
7 changed files with 467 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/operator-runbook.md
View File

@@ -21,6 +21,8 @@ mode are denied these by the permission classifier — that is intentional.
| `make test-ha-failover` | kills the primary PG pod to assert recovery |
| `make verify-activity-core` | reconciles activity-core runtime on railiance01 |
| `make reconcile-activity-core-llm-connect` | patches ConfigMap, applies llm-connect overlay, runs smoke pod |
| `make deploy-activity-core-triage-robustness` | deploys ACTIVITY-WP-0016 code/schema/runtime as a coupled bundle and triggers daily triage |
| `make admin-sync-smoke` | calls activity-core `POST /admin/sync` and proves worker pod identity/restart count did not change |
## Read-only / safe targets
@@ -33,3 +35,8 @@ Reconcile/verify targets post non-secret evidence notes to the State Hub
(`STATE_HUB_EVIDENCE_WORKSTREAM_ID` / `STATE_HUB_EVIDENCE_TASK_ID` env vars
attach them to a workstream/task). Never record Secret values — key counts
and readiness states only.
For `make admin-sync-smoke`, set `ACTIVITY_CORE_ADMIN_SYNC_FIXTURE_COMMAND`
when you need a specific enabled-flip/rename fixture before the sync call. The
command records whether a fixture ran; leaving it unset proves endpoint and
no-restart behavior only.