This was more annoying to figure out as this happened as some nodes happened to experience actual networking issues as this was going on, although it's possible networking issues on a node caused this to happen in the first place.…

kubernetes networking debugging zerotier