During a rolling update of a utility billing API, new Pods start but must not receive Service traffic until healthy. Which statement correctly ties readiness to rollout safety?
Select an answer to reveal the explanation.
Short Explanation
Don’t seat diners at a table that isn’t set. If readiness fails, the Pod stays off the Service endpoints, so clients keep hitting Ready Pods while the rollout waits for healthy newcomers.
Full Explanation
Readiness probes determine whether a Pod’s IP is included in Endpoints/EndpointSlices for matching Services. During RollingUpdate, unavailable (not Ready) Pods count against maxUnavailable math and prevent premature traffic shift. Liveness failures restart containers; they do not accelerate endpoint membership. Startup probes gate other probes early in Pod life but do not replace Services, and readiness failure does not auto-delete the Deployment.