A building-permit API Pod has started its process but is still loading reference data and cannot answer HTTP yet. How should orchestration’s service layer treat that replica?
Select an answer to reveal the explanation.
Short Explanation
A process can be alive and still useless to callers—like a ticket window with the lights on but the clerk still unpacking. Orchestration keeps not-ready replicas off the service endpoints. Ready means fit to serve, not merely started.
Full Explanation
Service load balancing should target ready endpoints. Readiness distinguishes “process started” from “able to serve traffic.” Sending traffic to booting or failing-readiness replicas causes errors. Node bootstrap success and Service deletion are unrelated substitutes for per-replica readiness. Probe object details come later; this item is the ready-versus-running idea.