liveBook · Manning

Readiness check

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

A Kubernetes readiness probe is a health check that indicates whether a container or application instance is ready to receive traffic.

A Kubernetes readiness probe tells the platform whether a microservice has started and can receive traffic. Kubernetes can therefore keep an instance out of service until its dependencies are available. section 11.2.8

Readiness differs from a liveness probe: readiness controls whether requests should arrive, while liveness indicates that the running service remains alive and accepting requests. section 11.2.8

HTTP readiness endpoint

Configure a gateway Deployment with a readiness probe that calls /ready on the container port after a five-second initial delay. Add /alive separately for liveness checks.

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

How deep it goes
Explains readiness alongside liveness and demonstrates HTTP configuration, but does not detail endpoint implementation.
Examples
Uses a gateway Deployment calling /ready and /alive over HTTP, plus a history service waiting for RabbitMQ.
What it assumes
Assumes Kubernetes Deployments, containers, HTTP endpoints, and microservice dependencies; contrasts with an earlier wait-port workaround.
What you can do after
Operate/configure Kubernetes Deployments with HTTP readiness and liveness probes for dependency-aware service availability.
How it connects
Connects readiness probes with liveness probes, Kubernetes Deployments, microservices, and upstream dependencies such as RabbitMQ.

Also explained in

Compare how 7 books explain readiness check →

Related concepts

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.