A readinessProbe on every permits API Pod calls a shared external payment dependency. During a brief payment outage, all Pods become NotReady. What is the main pitfall?
Select an answer to reveal the explanation.
Short Explanation
If every cashier’s ‘open’ light depends on one flaky credit terminal, the whole store looks closed during a blip. Tying readiness to a fragile external dependency can mark every Pod NotReady and empty Endpoints. Prefer checks that reflect this Pod’s ability to take work, with careful dependency policy.
Full Explanation
Readiness failures remove Pod IPs from Service Endpoints. When every replica’s readiness depends on the same external system, a dependency outage can mark the entire set NotReady and drop all traffic—even if Pods could still serve degraded or cached responses. Design readiness to reflect local readiness; handle dependency failure modes deliberately rather than blindly coupling probes to every upstream.