tegwick
bcb05f5d95
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> |
||
|---|---|---|
| .. | ||
| app-data-backup-restore-handoff.md | ||
| django-on-railiance.md | ||
| forge-source-of-truth-decision.md | ||
| forgejo-on-railiance01.md | ||
| inter-hub-on-railiance01.md | ||
| manifest-server-dry-run.md | ||
| operator-recipes.md | ||
| operator-setup.md | ||
| reuse-surface-on-railiance01.md | ||
| s5-app-onboarding-checklist.md | ||
| vergabe-teilnahme.md | ||