Liveness probe on /actuator/health/liveness, not the DB-aware aggregate

Shipped

September 16, 2026 at 8:23 PM UTC

Author

Kamo

Commit

2fde6cb

The aggregate /actuator/health includes the DataSource indicator, so restarting the database failed liveness on every pod at once and restarted the whole platform (~43 pods cold-starting together, ~4 min to recover). Liveness now answers only whether the JVM is alive; readiness and startup stay DB-aware, so a database outage sheds traffic without killing processes. Same split SecurityService already uses.