Readiness probe — are critical dependencies up? — GET /health/ready
Readiness probe — are critical dependencies up?
Kubernetes readiness probe. Checks PostgreSQL, MongoDB, and Redis connectivity concurrently. Returns 503 if any of those is unavailable so the load balancer stops sending traffic.
Endpoint: GET /health/ready
Authentication: No access token or API key is needed.
Parameters
Section titled “Parameters”This endpoint takes no parameters.
Request body
Section titled “Request body”No request body.
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
200 | Successful Response | Not documented (application/json) |
Response fields not documented. The API specification does not describe the body of every response this endpoint returns, so this page cannot list those fields. The body is not empty. To see it, call the endpoint on your own installation. All endpoints with undocumented responses.
Statuses not listed here are explained in Errors and retries.
More details
Section titled “More details”- Group: Health
- Operation ID:
readiness_health_ready_get - Source code:
backend/app/routers/health.py, line 249 - Specification: OpenAPI JSON