Right, etcd's entire focus is on being a consensus database for distributed systems needing coordination, locking, etc. So, eventually consistent WAN replication hasn't really been a focus.
I do think this sort of cross-cluster key replication is useful and we offer it as a userspace external tool called make-mirror[1].
[1] https://github.com/coreos/etcd/blob/master/etcdctl/README.md...
Worth noting that CockroachDB isn't using an eventually consistent model. Yes, it's not the same thing as etcd, but I can see some potential use case overlap.
There is some overlapping. But we should choose solution wisely :P.
Here is a doc [https://github.com/coreos/etcd/blob/master/Documentation/lea...] comparing etcd with other systems, including CockroachDB.
I work on etcd.
>What is your use case?
Contract work, so use case varies. I agree that etcd is often the right answer.