liveBook · Manning

Liveness check

As explained in Machine Learning Platform Engineering

A periodic check that determines whether a running workload should be restarted because its process is no longer healthy.

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

How Machine Learning Platform Engineering covers it

How deep it goes
Explains periodic endpoint calls and restart behavior, but does not provide probe configuration details.
Examples
Uses /healthz for liveness, /readyz for readiness, and BentoML’s built-in endpoints as concrete operational examples.
What you can do after
Operate/configure Kubernetes pod management around service liveness and distinguish restart checks from traffic-readiness checks.
How it connects
Connects liveness probes with health checks, readiness probes, Kubernetes, BentoML services, and Prometheus metrics.

Also explained in

Compare how 7 books explain liveness check →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Machine Learning Platform Engineering. The section links point to the parts of the book it draws on.