Watch
0
0
Fork
You've already forked hyperhive
0

readiness follows a cached store check instead of a constant or a login per probe

This commit is contained in:
maia 2026-11-19 06:07:18 +01:00 • committed by mara
commit b0239914b8

View file

@ -285,7 +285,10 @@ They answer 200 or 503 and send no body.
- `GET /readyz` is 200 while the daemon has what it needs to work: its queue
connection works (`swarm-stt`, `swarm-review-classifier`,
`swarm-notify-router`, `swarm-builder`, `swarm-claude-login`,
`swarm-nats-auth`), or it has bound its socket (the three auth responders).
`swarm-nats-auth`), or what it answers from is there: `swarm-logs-auth` and
`swarm-metrics-auth` are ready while the secret store answers,
`swarm-authelia-bridge` while its users file loads. The mechanics are in
[Readiness checks](../../4-implementation/swarm/readiness.md).
Nothing listens by default. Set `SWARM_STT_HEALTH_ADDR`,
`SWARM_REVIEW_CLASSIFIER_HEALTH_ADDR`, `SWARM_NOTIFY_ROUTER_HEALTH_ADDR`,
@ -299,4 +302,5 @@ daemon.
`swarm-controller` serves `GET /readyz` on its existing socket, next to
`/health`. It answers 200 while the queue connection works and the secret store
accepts the controller's login, and 503 otherwise.
answers the controller's login, and 503 otherwise (see
[Readiness checks](../../4-implementation/swarm/readiness.md)).