Skip to content

fix: serve a static /healthz for the platform startup/liveness probes - #2

Merged
reoring merged 1 commit into
mainfrom
fix/healthz-route
Oct 18, 2026
Merged

reoring merged 1 commit into
mainfrom
fix/healthz-route

Conversation

@reoring

@reoring reoring commented Oct 18, 2026

Copy link
Copy Markdown
Contributor

Problem

appthrust/platform#5029 (2026-10-11) set the nextjs-postgres template's probes to GET /healthz (startup, liveness) and GET / (readiness), taking appthrust/sample-nextjs#2 as the reference implementation. New apps, however, are generated from this template repository, which had no /healthz route. Result on appthrust.ink (facility-inspection-map-2, 2026-10-18): the container starts (✓ Ready in 0ms), the kubelet reports Startup probe failed: HTTP probe failed with statuscode: 404 and restarts it every two minutes; the Knative revision never becomes Ready and the platform release fails with KnativeReadinessDeadlineExceeded. Every app created from this template since 2026-10-11 is affected.

Change

  • app/healthz/route.ts: static 200 ok (force-static, no database access) — identical to sample-nextjs.
  • README: documents the probe contract (/healthz must stay static and database-independent).

Verification

npm ci && npm run lint && npm run build on the branch; build output lists └ ○ /healthz (Static).

appthrust/platform#5029 (2026-10-11) made the nextjs-postgres template probe
GET /healthz for startup and liveness, based on appthrust/sample-nextjs#2,
but apps are generated from this template, which had no such route. Every
app created from it since then was killed on its startup-probe 404 every
two minutes and never became Ready (appthrust.ink facility-inspection-map-2,
2026-10-18). /healthz is static and database-independent on purpose.
@reoring
reoring merged commit cda2a15 into main Oct 18, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant