Chris Luke

Sounds reasonable. I also wanted to split the test executable into a tests directory and setup that with some other tests.

This has been top of mind for me, so thanks for tackling it. Generating certs is the slowest part of topology creation in many cases!

@hasanrazaonline I am not aware of anyone else working on EVPN, but we (Comcast) will be digging into it soon, certainly for some MPLS-based use cases and possibly also VXLAN....

Do you have any excerpts from the meshnet daemon logs from both kube nodes? My guess is that they're not discovering each other so never get to the step where...

> Does it need dns for some part of this? > > ``` > # kubectl exec -n meshnet meshnet-8s7kt -- getent hosts meshnet.meshnet.svc.cluster.local > 100.73.91.37 meshnet.meshnet.svc.cluster.local > 100.73.91.38 meshnet.meshnet.svc.cluster.local...

> Think I figured this out. My CRI-O had proxy settings configured via systemd environment and whichever process/container was trying to make the off-host gRPC connections was trying to use...

The general problem with this suggestion is half the node implementations are outsourced to controllers who themselves create the services. There is little to no control over how they achieve...

I can't help with that specific issue, but fwiw on my physical cluster I setup metallb independently and tell KNE to not try to (I set the manifest to `""`).