A liveness check periodically calls a service endpoint to determine whether a running pod is alive and can continue its main process. When the check fails, Kubernetes may restart the pod to recover from a fault. section 10.4.1
In a BentoML service deployed to Kubernetes:
- The liveness probe calls /healthz and reports whether the pod is alive. section 10.4.1
- The readiness probe calls /readyz and determines whether the pod should receive traffic; readiness additionally requires operational request handling. section 10.4.1
- BentoML provides these health-check endpoints out of the box, alongside Prometheus metrics for service observability. section 10.4.1






