Readiness probe
Requires a working database pool. FIPS state and audit queue depth are reported but do not by themselves fail the probe: a deep queue spills to the write-ahead log rather than losing records, and removing the node from rotation would only push load onto its peers.
The detailed body is returned only when EXPOSE_HEALTH_DETAIL is on,
which it is not outside local environments, because this endpoint
answers before authentication. Otherwise only status is present.
Response
Ready for traffic.
ready, unavailable Incremented by every security-sensitive mutation. Each node polls it and treats cached decisions stamped with an older epoch as a miss, which is what makes a revocation take effect cluster-wide at once.