Lucas Servén Marín

@dajudge what's the status of this PR? Is it ready for a final review so we can merge and maybe include in a Kilo 0.6.0? :heart_eyes_cat:

Hi @anjmao, Support for cilium would be amazing. I've had this on my own ToDo list for a long time but have other higher priority work in the project, e.g....

Hi @anjmao do you have any update here? I know lots of people are interested in cilium compatibility and I would be happy to look at any WIP work and...

Kilo uses annotations on the node objects to override and force values that would otherwise be autonomously determined. Let's align this proposal with that practice, e.g. `kilo.squat.ai/force-wireguard-ip`. I think we...

An additional way to do this would be to continue listening on all interfaces but to require mTLS so all clients wanting to scrape have to present valid certs. In...

hi @chfxr that comment from your cloud provider is not correct. the HTTP endpoint at :1107 is only for informational purposed and has no effect on the functionality of kgctl...

I'm implementing protection for these endpoints using the [kube-rbac-proxy project](https://github.com/brancz/kube-rbac-proxy). The plan is for all requests to Kilo's endpoints to require a token that has the right to `GET` peers...

I would love for kilo to work on microk8s :) the fact that no error is printed but the node is never fully configured suggests to me that kilo cannot...

hi @carlosrmendes thanks a lot for that info, it's super helpful :) The `received incomplete node` message means that when the kilo agent listed the nodes from the API, a...