Clinic appointment Pods report Running but callers still see intermittent 502s during boot while dependencies warm up. Which probe should gate Service membership?
Select an answer to reveal the explanation.
Short Explanation
Running is "the process exists"; readiness is "you may send patients here." Keep a Pod out of Service endpoints until dependency checks pass so boot-time 502s never reach callers. That gate is the readiness probe.
Full Explanation
A Pod can be Running yet failing readiness; Kubernetes then omits it from Service endpoints. Readiness should mean the process accepts connections and required dependency checks succeeded. Liveness restarts stuck processes and is the wrong tool for temporary dependency warm-up. Assuming Running equals traffic-ready causes the clinic's boot-time 502 pattern.