Exercise 1: Liveness Failure vs. Readiness Failure — Different Actions — Possible Solution
====================================================================

LIVENESS PROBE FAILING: per the chapter, "a failed liveness probe
causes Kubernetes to kill and restart the container." The container is
considered broken/unresponsive, and Kubernetes' response is to
terminate it and start a fresh instance in its place -- this is the
mechanism that actually triggers container-level self-healing.

READINESS PROBE FAILING: per the chapter, the pod is "temporarily
removed from the Service's Endpoints... until it reports ready again,
with NO restart involved at all." The container is left running
completely untouched -- Kubernetes simply stops sending it new traffic
via the Service (Chapter 6), by removing it from that Service's
Endpoints list, until a SUBSEQUENT readiness check succeeds again, at
which point it's automatically added back to the Endpoints list and
starts receiving traffic once more.

The key distinguishing action: liveness failure = KILL AND RESTART the
container. Readiness failure = TEMPORARILY STOP ROUTING TRAFFIC to the
pod, with the container itself left running and untouched the whole
time. One is a destructive, corrective action aimed at a genuinely
broken container; the other is a non-destructive, temporary
traffic-management action aimed at a container that's alive but not
currently ready to handle requests well.

WHY THIS WORKS AS AN ANSWER
------------------------------
This states the exact, distinct action the chapter attributes to each
probe type failing -- restart vs. Endpoints removal -- and explicitly
names the underlying difference in SEVERITY/DESTRUCTIVENESS between
the two responses, which is exactly the distinction the chapter's own
warn-box calls out as commonly confused.