liveBook · Manning

Readiness check

As explained in Learn Docker in a Month of Lunches, Second Edition

A readiness probe is a Kubernetes container probe that determines whether a Pod should receive traffic from a Service.

A readiness check determines whether a Pod should receive traffic from a Service. When the check repeatedly fails, Kubernetes marks the Pod unready and removes its IP address from the Service endpoint list. section 15.3

Configure a container probe using one of these checks:

  • An HTTP request checks a response code, such as GET /healthz. section 15.3
  • A TCP check verifies that the application is listening on a port. section 15.3
  • A custom command runs a script containing multiple tests. section 15.3

HTTP readiness probe

Add readinessProbe under the container specification: readinessProbe: httpGet: path: /healthz, port: http; periodSeconds: 5. Apply the updated Deployment and watch Pod status with kubectl get po -l app=numbers -o wide -w.

How Learn Docker in a Month of Lunches, Second Edition covers it

How deep it goes
Explains probe types, timing, endpoint removal, and a runnable Deployment configuration, but does not detail probe thresholds.
Examples
Uses an HTTP GET request to /healthz every five seconds in a numbers-api Deployment.
What it assumes
Assumes familiarity with containers, Pods, Services, Deployments, and basic kubectl commands.
What you can do after
Operate/configure readiness behavior through Deployment YAML and verify Pod status with kubectl.
How it connects
Connects readiness probes with Pods, Services, Deployments, container probes, and liveness probes.

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 Learn Docker in a Month of Lunches, Second Edition. The section links point to the parts of the book it draws on.