Configuring health checks

Overview

This document touches on health checks for Runway services deployed in Cloud Run.

Runway service owners can define 2 types of healthcheck:

• startup: determines if a container has started and is ready to receive traffic.
• liveness: determines whether to restart a container. Depends on a successful startup probe.

For information on defining startup and liveness probes, refer to the Runway manifest schema. You may also refer to Cloud Run’s guide for more information and GCP recommended best practices.

NOTE: All Cloud Run services have a default TCP startup probe which tries to open a TCP connection on the container port.

Example of services using HTTP probes

• ai-gateway
• Runway’s example-service

Example of services using gRPC probes

• secret detection