service type : Nodeport
problem : can't access clusterIP:Nodeport
and find kube-proxy pod log like below
"can't open port, skipping it" err="listen tcp4 :32060: bind: address already in use" port={Description:nodePort for default/network-example2 IP: IPFamily:4 Port:32060 Protocol:TCP}
what is the problem??
This seems to be caused by a reported bug in the kube-proxy versions after v1.20.x (mine is v1.23.4). This fix is merged in the upcoming v1.24 release.
It is also confirmed in this issue that there would be no error if downgraded to the earlier release v1.20.1.
You can check if the process on the node that is using the port is kube-proxy itself. If this is the case, you could have hit a potential known issue of kube-proxy reported here.
