Investigate Consul vs. Etcd for service discovery
The Q1 OKR's include operationalizing service discovery for GitLab.com.
Current documents all refer to Consul as the service discovery mechanism. In the Geo Group Conversation this morning, @sytses had some good points about Etcd starting to look like the industry standard. Since we are moving towards being cloud native eventually, we will eventually be using Etcd as part of Kubernetes, and at that point we will have two solutions to support.
Consul is easier to use, and it is what we are currently using, but surely there is some value in supporting a single solution rather than two.
The Geo team is currently researching this issue (https://gitlab.com/gitlab-org/gitlab-ee/issues/8932). The @gitlab-com/gl-infra team should also look into it before work starts, and either document why Consul will be the better solution long term, or lay out a path to convert existing consul use to etcd.