Limit Elasticsearch Index to Groups Only
Problem to solve
In large self-managed instances developers may have projects that contribute to the company in group namespaces while smaller test/playground projects are in a personal namespace. Projects in the personal namespace are not valuable to be searched across the company and pollute the Elasticsearch index causing bloat and other unwanted side effects.
In the Elasticsearch administration we should support the ability to globally exclude personal namespaces from the index.
What does success look like, and how can we measure that?
In a successful implementation we'll see personal projects not indexed during the indexing process and we can measure this through instrumentation of the check box to count the number of instances where this is enabled.