Skip to main content

Check Readiness

GET 
/v1/ready

Check the runtime status of all the components of the runtime. If the service is ready, it returns an HTTP 200 status with the message "ready". If not, it returns a 503 status with the message "not ready".

The behavior for when an accelerated dataset is considered ready is configurable via the ready_state parameter. See Data refresh for more details.

Readiness Probe​

In production deployments, the /v1/ready endpoint can be used as a readiness probe for a Spice deployment to ensure traffic is routed to the Spice runtime only after all datasets have finished loading.

Example Kubernetes readiness probe:

readinessProbe:
 httpGet:
   path: /v1/ready
   port: 8090

Responses​

Service is ready