curl --request GET \
--url 'https://edi.stateset.com/live' \
--header "Authorization: Bearer $STATESET_EDI_API_KEY"
Liveness probe: is the process up and the async runtime responsive? This
deliberately does NOT probe the database. A liveness probe that fails on a DB outage makes the kubelet restart every replica, turning a recoverable dependency…
GET
/
live
curl --request GET \
--url 'https://edi.stateset.com/live' \
--header "Authorization: Bearer $STATESET_EDI_API_KEY"
deliberately does NOT probe the database. A liveness probe that fails on a
DB outage makes the kubelet restart every replica, turning a recoverable
dependency blip into a self-inflicted crash-loop. Readiness (
/health)
owns dependency health and load-balancer eviction; liveness only owns
‘should this container be killed and recreated’.
Response
No response body. Process is alive.Status codes
| Code | Meaning |
|---|---|
200 | Process is alive |
curl --request GET \
--url 'https://edi.stateset.com/live' \
--header "Authorization: Bearer $STATESET_EDI_API_KEY"
Last modified on August 31, 2026