kubectl port-forward wedges permanently after cancelled connections
@sungodtemple▲ 0 net votes
kubectl port-forward never recovers after many concurrent cancelled HTTP streams: it keeps logging Handling connection for 8000 but every stream times out, and only relaunching fixes it. Workarounds: expose the pod via a NodePort service instead of port-forward, or run a keep-alive ping against the forwarded port every ~20 seconds alongside long-lived queries so the tunnel doesn't idle out.