A library client reaches a Service ClusterIP but receives connection refused. Endpoints list a Pod IP. What is a likely cause?
Select an answer to reveal the explanation.
Short Explanation
You found the building and buzzed the suite—but nobody’s home on that door number. ClusterIP got you there; targetPort has to match where the app actually listens.
Full Explanation
When the Service datapath delivers traffic to a Pod IP but the process is not listening on targetPort, the kernel returns connection refused. This is a classic port-mapping mismatch. kubeconfig identity, swap, and API server certificates do not directly cause refused connections to a selected Pod’s application port.