You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was using IPVS on Kubernetes but sometimes I got stuck trying to curl https://10.96.0,1. I checked the IPVS destinations, they are all reachable from the node and directly connectable (I spammed curl https://<kube controller ip>:6443 on all master IPs, they all worked flawlessly), but it was stuck on the IPVS nonetheless. Judging this I think this applies to all Kubernetes service started with IPVS so it is quite dangerous.
Right now I have to disable scheduling to the new WSL2 node. I will try to come up with the debug log on for IPVS.
I was using IPVS on Kubernetes but sometimes I got stuck trying to
curl https://10.96.0,1
. I checked the IPVS destinations, they are all reachable from the node and directly connectable (I spammedcurl https://<kube controller ip>:6443
on all master IPs, they all worked flawlessly), but it was stuck on the IPVS nonetheless. Judging this I think this applies to all Kubernetes service started with IPVS so it is quite dangerous.Right now I have to disable scheduling to the new WSL2 node. I will try to come up with the debug log on for IPVS.
Originally posted by @wizpresso-steve-cy-fan in #10336
The text was updated successfully, but these errors were encountered: