Leon Löchner

i think it is because your laptop's endpoint is discovered since #146 and now Kilo wants to reapply the spec of your Laptop's peer that has a nil endpoint because...

What is the Peer spec of your laptop. Did you set persitent-keep-alive to 0? Because the endpoint is not updated if it is 0: https://github.com/squat/kilo/blob/05e8ded744207571389e208353209016c449ba79/pkg/mesh/topology.go#L275

Hi @Sandah, Sorry for the late reply. Kilo is using the API server for key exchanges, discovery of endpoints, etc. This means the kubernetes control plane has to exist before...

Maybe it is not related, but some things seem odd to me. Your nodes have private IPs and you are using `mesh-granularity=local`, but still the nodes are WireGuard peers of...

#104 allows nodes that have __no__ private IPs. Prior to the PR, the internal IP was set to the public IP, when no private IPs were found. Now with #104...

> * using the `--private-networking=false` flag disables private networking on a node This might not make sense because Kilo is normally run as a DaemonSet, so using this flag will...

> * setting `kilo.squat.ai/force-internal-ip=""` on a node disables private networking for the node This was implemented in #127.

You can override the default with the `listen` flag. Like `kg - - listen localhost:1107`. If you want to query metrics from a remote host or different pod, you would...

Apparently the PersistenKeepalive is only meant for the client (Peer) configuration. If you would change the current behavior of the `topology.Conf()` function, you would make all your nodes with a...

> However, all cluster nodes are on the same network/in the same location, where the PersistentKeepalive annotation on the node would not be needed as well. My thinking was that,...