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

Route issue-core directly on railiance01
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source
This commit is contained in:
tegwick 2026-08-19 23:41:57 +02:00
parent 41a3fb8b81
commit 213e810cf8
3 changed files with 16 additions and 127 deletions
Download patch file Download diff file Expand all files Collapse all files

4
k8s/railiance/README.md
View file

@ -33,6 +33,10 @@ issues). Set `rest` only for intentional issue-core projection when the backend
is healthy. `ISSUE_CORE_API_KEY` and `FORGEJO_TOKEN` are synced from OpenBao into
`actcore-runtime-secret` by ExternalSecrets.
`ISSUE_CORE_URL` uses the private cross-namespace Service directly:
`http://issue-core.issue-core.svc.cluster.local:8765`. The historical
host-network bridge and workstation tunnel are not part of this deployment.
**Ops run claim queue (ACTIVITY-WP-0026):** ConfigMap sets
`OPS_RUN_QUEUE_ENABLED=true`. After image + migrate job (alembic **0007**),
workers insert claimable `ops_runs` on emit. Full railiance checklist: