Public-health Pods keep running but fail readiness probes. How does…

Question

Public-health Pods keep running but fail readiness probes. How does that affect a Service that selects those Pods?

Accepted Answer

Not-ready Pods are removed from the Service Endpoints so traffic is not sent to them until they become ready. — Failing readiness is like putting a "closed" sign on a register — the Pod stays in the store, but the Service stops sending customers there.

Answer

Failed readiness probes delete the Service object and recreate it with type NodePort.

Answer

Not-ready Pods remain in Endpoints but kube-dns stops resolving the Service name entirely.

Answer

Readiness failures convert the Service to headless automatically until probes pass.

Public-health Pods keep running but fail readiness probes. How does that affect a Service that selects those Pods?

Short Explanation

Full Explanation