Aaron U'Ren

@fujita Thanks again for continuing to pursue this with us. You mentioned that you didn't think that `LocalRestarting` should be set in our case. And in the case of @rkojedzinszky's...

Looking at this... I was playing with this in my own cluster a few days ago, and definitely see the TCPMSS clamping rules in the chain (similar to the output...

Ok, after looking into this some more, it seems that I was using a non-DSR VIP the first time I was testing it. :man_facepalming: Anyway, after selecting the correct VIP...

I don't run k0s so it might be a while before I can find time to setup an environment and test it myself. However, it sounds like kube-router may not...

@manuelbuil - Thanks for the quick feedback! After thinking about this just a bit more in my spare time this weekend, I feel like resetting the ipset handlers so far...

I submitted a fix for this in #1666 I tested it with the example that you gave and it worked correctly for me. However, I'd prefer another set of eyes...

Hmm... That's pretty odd. I agree that you should be seeing some kind of error. The health of the pod is reported by the health check controller, this is what...

hmm... That is pretty odd. Looking back up at your event log, I can see now that it actually says: ``` Warning Unhealthy 11m kubelet Liveness probe failed: Get "http://10.19.91.100:20244/healthz":...

Note, that kubelet is not curling localhost to get the health of kube-router, it is using the IP of the interface to the node, so that may be a difference...

From what I can tell, kube-router isn't crashing, at least not in any of the logs that you've sent so far, it seems to be being killed.