kaiyou

Maybe a flag to specify the delay between rejoins, with a default value that disables the feature? Or a different, more explicit `--persistent-nodes` to distinguish between initial and later rejoins.

A couple important issues that need be addressed for rotation to work properly (I am probably stating the obvious, but let's do it anyway): - specify when a new key...

Here is a concrete idea for implementation. The requirement is that a single node is responsible for triggering a rotation. That responsibility could be static (a configuration flag) or dynamic...

That last one is probably a lot simpler to implement. We would still need some ipc, possibly a control socket for wesher or some inotify. But it sounds a lot...

I plan on working on something a bit different, but I might end up supporting both. First my use case in a sentence (I'll develop in another issue): multiple k8s...

For implementation, I intend on using this : https://godoc.org/github.com/vishvananda/netlink#RouteSubscribe I will implement a new loop, identical to the cluster loop, consuming events from netlink, filtering the routes using a configuration...

Here is the current state of our work on the routing matter. It will undergo some tests in our use case in the next few days: https://github.com/kaiyou/wesher/tree/feature-routed-net

This is currently running on three different clusters of mine, properly propagating kubernetes routes. I will provide production feedback next week.

First please accept my apologies for posting to this thread dedicated to your meetings and minutes, I was directed here by @parisni and I have nothing but kind words for...

Agreed with the quick fix, and more generally we could take advantage of that map to use specific relays.