Better Elasticsearch support for GitLab Geo
What are you trying to do? Articulate your objectives using absolutely no jargon.
Add the ability to specify Geo Elasticsearch Nodes or clusters
How is it done today, and what are the limits of current practice?
Currently, GitLab Geo uses the Elasticsearch application settings and therefore the same Elasticsearch cluster as the primary. As a Geo Instance is setup, in a diffrent region. The same Elasticsearch Cluster will be used and not take advantage of the Value of multiplue zones.
ZD: https://gitlab.zendesk.com/agent/tickets/46518
What's new in your approach and why do you think it will be successful?
By Specifing the Geo Specific Cluster and auth, the GitLab instance can be used in other locations.
Who cares? If you're successful, what difference will it make?
Advanced Search with elasticsearch is a critical feature to Big Code customers. These are often times the Same customers who need HA and Geo.
What are the risks and the payoffs?
If a Customer needs to rebuild there Indexes this can take days for Repos that are 2 TB + , Not only would this mean search features would take longer to recover, there would also be a perfromance strain to account for Workers that will build the index.