Liveness + readiness probe
Health & Monitoring
Liveness + readiness probe
Returns 200 when healthy, 503 when any mandatory dependency (storage, scheduler, message bus, grpc) is degraded. The body carries per-component status so orchestrators can show which specific thing is broken.
GET
Liveness + readiness probe
Response
Healthy
Application version with build information
Overall health status
Available options:
healthy, degraded Detailed status
Available options:
ok, error Whether the service is ready to accept requests
Service uptime in seconds