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

Prepare ISSUE-WP-0007 railiance01 migration
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source
This commit is contained in:
tegwick 2026-08-19 20:23:28 +02:00
parent 6f93eb7fc0
commit 86973f279a
4 changed files with 190 additions and 64 deletions
Download patch file Download diff file Expand all files Collapse all files

13
workplans/ISSUE-WP-0003-railiance01-deployment.md
View file

@ -1,7 +1,7 @@
---
id: ISSUE-WP-0003
type: workplan
title: "Deploy issue-core as a service on railiance01 (ArgoCD GitOps pilot)"
title: "Historical CoulombCore deployment and railiance01 bridge (initially mislabeled as railiance01 GitOps)"
domain: infotech
repo: issue-core
status: finished
@ -14,6 +14,17 @@ state_hub_workstream_id: "896ace77-21b3-450b-8fb7-254aefc8c570"
# Deploy issue-core as a service on railiance01 (ArgoCD GitOps pilot)
> **Historical topology correction (2026-08-19):** This workplan is finished
> because it did deploy and prove issue-core, but the Deployment and ArgoCD
> Application were on **CoulombCore**, not railiance01. The real railiance01
> consumed the service through the two-hop ops-bridge lane documented in the
> 2026-07-02 completion section. Railiance01 currently has an empty `issue-core`
> namespace and no ArgoCD. See
> `history/2026-08-19-wp-0003-topology-correction.md` and ISSUE-WP-0007 for the
> direct railiance01 migration. The paragraphs below are retained as historical
> evidence; unqualified "railiance01 cluster" claims refer to the mistaken
> topology understanding at the time.
`issue-core` is the authoritative task-lifecycle manager and the REST ingestion
target for activity-core's `IssueSink`. Deployment artifacts are on `main`
(`Dockerfile`, `docker-entrypoint.sh`, `k8s/railiance/`); image