A liveness probe is a Kubernetes health-check configuration that determines whether a container or pod is still functioning and should continue running.
A liveness probe tells Kubernetes whether a running container or pod is still alive and accepting requests. When the probe reports failure, Kubernetes can restart the unhealthy workload instead of leaving it stuck. section 11.2.8
Use liveness checks alongside readiness checks:
Readiness indicates that a service has started and can accept requests; liveness indicates that it remains operational afterward. section 11.2.8
Health checks also handle dependencies that become unavailable later, such as RabbitMQ during crashes, upgrades, or maintenance. section 11.2.8
How Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform covers it
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 it assumes
Assumes Kubernetes Deployments, containers, and service health endpoints; distinguishes readiness from liveness probes.
What you can do after
Configure Kubernetes Deployments with HTTP liveness probes that support automatic recovery from unhealthy services.
How it connects
Connects liveness probes with readiness probes, Kubernetes, microservices, and upstream dependencies such as RabbitMQ.
Kubernetes in Action, Second EditionA liveness probe is a Kubernetes health check that determines whether a container's application is functioning and can trigger container termination after failure.
Kubernetes for DevelopersA liveness probe is a Kubernetes health check that determines whether a running container is still functioning and should be allowed to continue running.
Machine Learning Platform EngineeringA periodic check that determines whether a running workload should be restarted because its process is no longer healthy.
Quarkus in ActionA Kubernetes liveness probe periodically determines whether a container should be restarted because its application is no longer recoverable.
Spring in Action, Sixth EditionA liveness probe is a health indicator that tells an orchestrator whether an application is healthy enough to continue running without being restarted.
health checkkind of · A health check is an assessment or probe that determines whether a system, service, or component is functioning acceptably according to defined criteria.
Kubernetesused by · Kubernetes is an open-source platform for orchestrating and automating the deployment, scaling, and management of containerized workloads across computing clusters.
readiness checkcontrasts with · A readiness check is a health probe that determines whether a running service or workload is prepared to receive requests or traffic.
exec probeincludes · An exec probe is a Kubernetes probe that runs a command inside a container and evaluates whether it exits successfully.
health check endpointuses · A health check endpoint is an API endpoint that reports whether an application or service is operating correctly or ready to handle requests.
This explainer was generated by Manning's knowledge graph from the text of Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform. The section links point to the parts of the book it draws on.
