By default, when a Pod fails its readiness probe, how does that affect Service traffic?
Select an answer to reveal the explanation.
Short Explanation
Readiness is the “open for business” light. Fail it, and the Service stops sending customers to that Pod—Endpoints drop the IP—while the Pod may still be alive. It’s traffic control, not an instant kill switch from kube-proxy.
Full Explanation
Failing readiness removes the Pod from the Service’s ready Endpoints (or marks it not ready in EndpointSlices), so the Service stops load-balancing new connections to that Pod. The Pod is not deleted by kube-proxy, containers are not frozen solely for that reason, and the Service ClusterIP is not reallocated when a backend fails readiness.