Steffen Vogel

> You do still have to run kube-proxy otherwise you can't resolve service IPs though. Maybe just setting a route for the service CIDR towards an in-cluster node/kube-proxy would be...

I would add a paragraph describing how Kilo handles routing. Especially the difference when used in standalone/CNI and addon mode.

A quick note for the NAT-to-NAT documentation: Endpoint discovery only works for nodes with a persistentKeepalive greater than 0.

Hi @colemickens, I started to work on an independent project which implements this: [cunicu](https://github.com/stv0g/cunicu) (formerly WICE). Its still under active development and not ready for use or integration into kilo...

Hi @squat, I am working on cunicu as part of my job as a researcher. Thats why there is a funding acknowledgement in the readme. In the last days, progress...

Hi @muvaf, Sure, I've got a bit stuck over the last weeks with other projects. But I plan to pick up the work pretty soon. The main repo is [WICE](https://github.com/stv0g/wice)....

Hi @muvaf, My current plan is to make cunicu and Kilo interoperable. Meaning that Kilo will handle peer discovery and cunicu will handle the endpoint discovery. But adding Peer discovery...

I think the insight @squat gave in this issue should be integrated in the documentation (see #165) Other than that, I guess we can close the issue?

@msdean I seem to have the same issue as you.

Okay, I solved it: libnftl uses TVLs to encode different types of fields in the UserData attribute. This has been added via this patch: https://git.netfilter.org/libnftnl/commit/?id=5c3bc232dc9d1dd01d589fab096f67d944621fc2 Here is some quick example...