Support Prometheus on its own server / container
With GitLab support for GKE improving, it would be helpful to also improve how Prometheus is packaged when deployed in this environment. We should also work to support environments where an end-user may not want to run Prometheus on the same server as Omnibus, but rather on its own.
We should support setting up Prometheus on its own, whether it be manual by an administrator or automatically when deployed with a scheduler like Kubernetes. This would reduce the performance impact of monitoring on the core GitLab service, and better align the architecture for container based deployments.
To accomplish this, we would need to:
TBD - Enhance
gitlab.rbto support launching Prometheus by itself (may not be any work required)
- TBD - Ensure GitLab can discover provisioned Prometheus server IP when deployed separately