24 lines
1.2 KiB
Markdown
24 lines
1.2 KiB
Markdown
# WP-0003 topology correction — 2026-08-19
|
|
|
|
ISSUE-WP-0003 deployed and verified issue-core, but its opening narrative
|
|
misidentified the target cluster. Its own 2026-07-02 completion note records
|
|
the corrected topology:
|
|
|
|
- ArgoCD, the `issue-core` namespace, Service, ExternalSecret, and Deployment
|
|
were on the CoulombCore k3s cluster.
|
|
- The real railiance01 cluster ran activity-core and reached issue-core through
|
|
`actcore-issue-core-bridge` plus two ops-bridge forwards via the workstation.
|
|
- An authenticated activity-core-shaped request traversed that path and created
|
|
external issue 176, so WP-0003's functional proof remains valid for the
|
|
historical deployment.
|
|
|
|
The 2026-08-19 observation that railiance01 has an empty `issue-core` namespace
|
|
and no ArgoCD is therefore not evidence that a railiance01 workload was pruned
|
|
or silently lost. The workload was never directly deployed there. The defect
|
|
was the workplan's stale opening summary and title after its later topology
|
|
correction.
|
|
|
|
ISSUE-WP-0007 supersedes that topology. It keeps the reusable container,
|
|
secret, health, and authenticated-ingestion evidence while moving runtime
|
|
packaging into `rapp-issue-core` and placing the service directly on
|
|
`reef-railiance` / railiance01.
|