Open aberfeldy opened 5 years ago
Morning, @aberfeldy Correct me if I am wrong - your backends register themselves in etcd by putting some KeyValue, using unique key with known prefix, like "backend-1", "backend-2", specifying lease and updating it, so that when backned is offline, KeyValue disappears?
The idea was to run it in front of a kubernetes cluster as a load balancer for the worker nodes and use kubernetes etcd to register the nodes. So yes when a node goes offline it should not be visible as an alive node in etcd and thus not be served by gobetween.
I've described universal pattern, not related to cubernetes. Maybe we should make both - cubernetes specific and generic
Morning, any plans on adding support for etcd as a discovery option to gobetween? It would be a nice addition, especially with self hosted Kubernetes nodes.