Description
Hello.
We had netbird client installed on a Linux VM (not as container, normal installation via curl -fsSL https://pkgs.netbird.io/install.sh | sh) that run Rancher / Kubernetes.
Everything was working fine. The Netbird client made connections successfully to the managmenet node and also this node that netbird was running was acting as a network peer just fine.
The problem happened when we restarted this VM for the first time.
We saw that our Kubernetes services were not running correctly and all boiled down to calico / flannel that kubernetes uses.
We think because wireguard interface wt0 loads at startup because netbird service starts automatically and doesn't let the calico / flannel establish first, results in Pod-to-pod communication to be broken.
Maybe netbird client in future releases can handle this scenario better?
Thank you.