liveBook · Manning

Liveness check

Also called liveness probe

A liveness check is an automated health test that determines whether a running workload remains functional or should be restarted.

How 8 Manning books explain it

Kubernetes in Action, Second Edition

A liveness probe is a Kubernetes health check that determines whether a container's application is functioning and can trigger container termination after failure.

How it is used
Detects applications that stop functioning while their processes continue running, so Kubernetes can terminate unhealthy containers.
How deep it goes
Explains three probe mechanisms, manifest settings, failure thresholds, restart observation, and handler design; does not develop a complete application health endpoint.
Examples
Uses a two-container HTTP probe manifest, a forced HTTP 503 observed through kubectl events, and a combined startup-and-liveness manifest.
What you can do after
Operate/configure it by choosing a probe, setting failure timing, and inspecting events and restart counts after a failure.

Read how Kubernetes in Action, Second Edition explains liveness check →

Kubernetes for Developers

A liveness probe is a Kubernetes health check that determines whether a running container is still functioning and should be allowed to continue running.

How it is used
Signals when Kubernetes should restart a running but stuck or unresponsive workload.
How deep it goes
Explains probe behavior, HTTP endpoint design, failure tolerance, and a command-based worker check, without exhaustively cataloging probe options.
Examples
Uses an HTTP health endpoint, a database-connection scenario, and a worker timestamp checked by a shell command.
What you can do after
Operate/configure it with a Deployment livenessProbe and choose an HTTP or command check suited to the workload.

Read how Kubernetes for Developers explains liveness check →

Machine Learning Platform Engineering

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

How it is used
Protects Kubernetes-hosted inference services by detecting failed processes and enabling pod recovery.
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.

Read how Machine Learning Platform Engineering explains liveness check →

Designing AI Systems

A liveness probe is a health-check interface that indicates whether a running service instance is alive and able to be managed by infrastructure.

How it is used
Uses a simple HTTP endpoint to let an orchestrator detect unrecoverable containers and restart them.
How deep it goes
Explains status semantics, failure cases, shutdown boundaries, and dependency-scope tradeoffs, but stops short of implementation code.
Examples
Uses startup initialization, deadlock recovery, graceful shutdown, and Kubernetes rolling deployment as operational examples.
What you can do after
Operate containerized services with separate liveness and readiness behavior and avoid coupling restarts to dependency health.

Read how Designing AI Systems explains liveness check →

Learn Docker in a Month of Lunches, Second Edition

A liveness probe is a Kubernetes container probe that determines whether a container should be restarted.

How it is used
Uses a container health endpoint to trigger restarts when an application instance repeatedly fails.
How deep it goes
Defines HTTP checking, intervals, and restart effects without detailing failure thresholds or probe internals.
Examples
Uses an HTTP GET request to /healthz every 20 seconds in a numbers-api Deployment.
What you can do after
Operate/configure Kubernetes Deployments with an HTTP liveness probe and verify Pod restarts using kubectl.

Read how Learn Docker in a Month of Lunches, Second Edition explains liveness check →

Quarkus in Action

A Kubernetes liveness probe periodically determines whether a container should be restarted because its application is no longer recoverable.

How it is used
Uses an HTTP health endpoint as the target for Kubernetes liveness probes, enabling restarts when an application cannot recover.
How deep it goes
Defines failure meaning and Kubernetes response, but does not detail probe timing configuration or custom liveness implementation.
Examples
Uses /q/health/live, the SmallRye Health extension, Dev UI, and aggregate JSON health output as concrete artifacts.
What you can do after
Operate health monitoring by adding SmallRye Health and querying aggregate or liveness-specific HTTP endpoints.

Read how Quarkus in Action explains liveness check →

Spring in Action, Sixth Edition

A liveness probe is a health indicator that tells an orchestrator whether an application is healthy enough to continue running without being restarted.

How it is used
Uses Actuator health groups to let Kubernetes decide whether to keep an application running or replace its pod.
How deep it goes
Defines liveness, contrasts readiness, and shows Spring Boot and Kubernetes configuration without detailing probe implementation internals.
Examples
Shows application.yml probe enablement, Kubernetes HTTP probes, and programmatic LivenessState availability events.
What you can do after
Operate/configure Spring Boot and Kubernetes liveness probes for restart decisions and distinguish them from traffic readiness.

Read how Spring in Action, Sixth Edition explains liveness check →

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform

A liveness probe is a Kubernetes health-check configuration that determines whether a container or pod is still functioning and should continue running.

How it is used
Uses Kubernetes health checks to detect stuck microservices and trigger automated restarts.
How deep it goes
Explains probe roles and shows HTTP Deployment configuration, without detailing endpoint implementation.
Examples
Uses a gateway Deployment with /alive and /ready HTTP endpoints and a history service depending on RabbitMQ.
What you can do after
Configure Kubernetes Deployments with HTTP liveness probes that support automatic recovery from unhealthy services.

Read how Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform explains liveness check →

Also covered in

What to know first

Related concepts

Questions about liveness check

What is liveness check?

A liveness check is an automated health test that determines whether a running workload remains functional or should be restarted.

Which Manning books explain liveness check?

Kubernetes in Action, Second Edition, Kubernetes for Developers, Machine Learning Platform Engineering, Designing AI Systems, Learn Docker in a Month of Lunches, Second Edition, Quarkus in Action, Spring in Action, Sixth Edition and Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform.

What should I know before learning liveness check?

Manning books that teach liveness check usually introduce container, HTTP status code and load balancing first.

What is the difference between liveness check and readiness check?

A liveness check is an automated health test that determines whether a running workload remains functional or should be restarted. A readiness check is a health probe that determines whether a running service or workload is prepared to receive requests or traffic.

What kinds of liveness check are there?

Kinds of liveness check include exec probe.

What is liveness check a kind of?

Liveness check is a kind of health check. A health check is an assessment of whether a system, service, or component is functioning acceptably and is available or ready for its intended work.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.