Chen, Dylan

BTW, due to continuous observing I found that even if the ip route is correct, however it also may get stuck on coredns pod creating, but if I re-run it...

Hi @onong Bad luck that it reproduced today with correct route, here is for your information to address the root cause. ## kubectl get pods -A -o wide ``` NAMESPACE...

> > Absolutely magic for the next hop, suppose if the networking switched into DHCP and assuming that the two ports allocated ips under the same subnet, how can it...

New finding that it always happens in such scenario that the created `tap` interface mac address changed. Here is a workaround that when I change back the physical mac address,...

Another new findings: kubernetes worker joining cluster failed due to created `tap` device mac address also changed