Migrate etcd backend to APIv3 client about libkv HOT 5 OPEN

Call to @aluzzardi, @sanimej and @vieux to shed some light on the activity status of docker/libkv and docker/leadership. Should I contribute etcd3 support here, or do it directly in the traefic repository to have this issue fixed?

from libkv.

@abronan if I would provide a pull request for this, should this replace the current etcd v2 setup, or should I provide a separate etcd3 backend?

from libkv.

Hi @ringods, thank you for tackling this. I think this should be a separate etcd3 backend as I'm not sure that backward compatibility is maintained (the distributed lock implementation might change between v2 and v3 for example).

Although before putting in the work I would recommend getting a status from the maintainers of the repository. I'm no longer maintaining it and it does not seem to be actively maintained anymore.

I thought about forking as many people may still rely on it but I'm not sure I can invest time maintaining a fork for now.

from libkv.

I found work in progress on etcd3 in this fork:
https://github.com/dqminh/libkv/tree/etcdv3/store/etcdv3
@dqminh, you need a hand finishing it?

from libkv.

@ringods I'm also interested in the v3 support, ping me if more help is needed.

from libkv.