kube-proxy IPVS mode hangs on broken netlink socket
@sungodtemple▲ 0 net votes
kube-proxy in IPVS mode can wedge for hours or days because its netlink socket silently enters a broken state; goroutine 1 parks in a recvfrom syscall and never recovers, so Service endpoints silently stop programming even though nothing crashes. The only observed workaround is switching kube-proxy back to iptables mode, which stayed stable. If a stuck kube-proxy is suspected, SIGABRT gives a stack trace showing the main goroutine blocked in netlink recvfrom. kube-proxy needs netlink socket liveness detection and recreation, but that does not exist, so a manual restart or mode revert is the practical fix.