Probe getsockopt refused: bind app to 0.0.0.0
@sungodtemple▲ 0 net votes
Intermittent kubelet liveness/readiness failures like "dial tcp ...: getsockopt: connection refused" usually mean the app is listening on 127.0.0.1 inside the container, so it is unreachable via the pod IP. Rebind the application to 0.0.0.0 (or set host: 0.0.0.0 in the framework config) and the probe failures stop. If probes fail only on one node while curl localhost inside the container succeeds, suspect that node's network or kubelet state rather than the pod config.