A Service exists, its Endpoints list Ready Pod IPs, yet curls to the Service port hang. Containers listen on 9090 but targetPort is 8080. What is wrong?
Select an answer to reveal the explanation.
Short Explanation
Endpoints only prove “which Pods,” not “which door on the Pod.” If targetPort is 8080 and the process listens on 9090, you’re knocking on an empty room. Fix targetPort (or the app port) so they match.
Full Explanation
Endpoints membership shows selected Ready Pods; kube-proxy still forwards to each Pod using the Service’s targetPort. If targetPort does not match the container listen port, connections fail even though Endpoints look populated. A second Service is not required, DNS is not the only suspect, and NodePort is unrelated to fixing a targetPort mismatch.