coulomb/railiance-apps
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record e3ae22e deploy and flag /health ingress routing bug
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
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>
This commit is contained in:
tegwick 2026-07-07 20:14:29 +02:00
parent a2c0da13c2
commit bcb05f5d95
1 changed files with 16 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

18
docs/reuse-surface-on-railiance01.md
View file

@ -104,8 +104,22 @@ reuse-surface hub list
curl -fsS "$REUSE_SURFACE_URL/v1/federated" | jq '.capabilities | length' curl -fsS "$REUSE_SURFACE_URL/v1/federated" | jq '.capabilities | length'
``` ```
Deployed image tag: see `helm/reuse-surface-values.yaml` (currently `cb7a6e4`). Deployed image tag: see `helm/reuse-surface-values.yaml` (currently `e3ae22e`,
Dogfood: `reuse-surface` repo registered; federated index returns 12 capabilities. deployed 2026-07-07 for REUSE-WP-0019-T01/T02).
Dogfood: `reuse-surface` repo registered; federated index returns 61 capabilities.
**Known issue (found 2026-07-07, not fixed):** the public ingress serves
`GET /v1/*` correctly but 404s on the exact-path `/health` rule — Traefik
appears to shadow it with the catch-all `/` rule routed to
`reuse-surface-landing`. Confirmed NOT a pod/service problem: `/health`
works correctly via direct port-forward to `svc/reuse-surface`, and the
Deployment's own internal readiness/liveness probes (which hit `/health`
directly, bypassing ingress) pass fine — the pod is `1/1 Ready`. Only
public external monitoring against `https://reuse.coulomb.social/health`
is affected; real API clients using `/v1/*` are unaffected. Needs an
explicit Traefik router priority annotation (or a path-rule reorder) on
`charts/reuse-surface/templates/ingress.yaml` — deliberately not changed
here since it's a shared production ingress edit outside this task's scope.
## Operations ## Operations