Commit graph

7 commits

Author SHA1 Message Date
bcb05f5d95 Record e3ae22e deploy and flag /health ingress routing bug
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Found while smoke-testing the REUSE-WP-0019-T01/T02 deploy: GET
/v1/federated works (200) but the exact-path /health rule 404s at the
Traefik edge, shadowed by the catch-all / rule to reuse-surface-landing.
Confirmed pod/service-level health is fine (direct port-forward works,
readiness/liveness probes pass, pod is 1/1 Ready) -- this is an ingress
routing config issue affecting external monitoring only, not the API
itself. Not fixed here; needs a Traefik router priority annotation on
charts/reuse-surface/templates/ingress.yaml, a deliberate change to shared
production ingress outside this task's scope.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-07 20:14:29 +02:00
c7d49d3102 Handle app deployment guardrail suggestions 2026-06-15 22:07:03 +02:00
b859530fcf Add reuse service landing page 2026-06-15 15:40:57 +02:00
07ad27176e Note bootstrap removal and DNS propagation on production IP 2026-06-15 10:31:16 +02:00
7c05877f1e Correct reuse-surface target: Railiance01 92.205.62.239
Document production vs CoulombCore bootstrap IPs and deploy via
config-hosteurope. Public DNS for reuse.coulomb.social still wrong.
2026-06-15 10:24:32 +02:00
77aa0d76f5 Finish RAILIANCE-WP-0007: reuse-surface hub deployed on railiance01
Helm revision 3 with image cb7a6e4. Runbook updated with TLS/DNS operator
guidance and smoke-check commands.
2026-06-15 10:15:36 +02:00
37a5c2f690 Record reuse.coulomb.social DNS; add deploy runbook; close T03 2026-06-15 09:45:17 +02:00