Toon Sevrin

No idea, but note that behind the scenes, this project takes the same Daemonset approach as you said was not applicable.

oooh of course, yeah you just need your ingress to be a daemonset, within my company, we simply patch our istio ingress-gateway deployment to a daemonset (with hostPorts) and it...

I got blocked by some weird Akrobateo behavior as well. Go back to DaemonSets. All I had to do for this was apply [a few small patches](https://gist.github.com/toonsevrin/22b110d3c1d2eaa365c1bb6def44ade7#file-istio-operator-yaml-L29-L37) to my ingress...

Well as long as you can setup a proxy for that your golden! Note that this is also how Akrobateo works :)

Well this is an easy problem! Just add a healthcheck endpoint to your daemonset service (eg. /healthz) :tada: If you have a DNS with health checks (and you don't mind...

> Hi @jawabuu, > From my experience with Metallb/Akrobateo (and ExternalDns)) the IPs at question are not the ones of the masters nodes. In Metallb they are from a pre-defined...

@jawabuu If you're able to add it as metadata (eg. header), you'll be the happiest. That way you don't have any networking challenges. hostPort Daemonsets (eg. akrobateo) should receive packets...

For everyones interest, I've noticed [inlets](https://github.com/inlets/inlets-operator), a project that seems similar to akrobateo, but is maintained.

I'd like this as well.

I'll write a snapcraft package, hopefully this can then be CDed with the [slack publisher](https://snapcraft.io/slack). EDIT: A snapcraft package has already been written: https://github.com/jwallden/nebula-snap