GitLab Next

Description

We are now able to deploy Prometheus servers to connected Kubernetes clusters with a single button (https://gitlab.com/gitlab-org/gitlab-ce/issues/41053). With GitLab's multi-cluster support, this can mean either a single or multiple Prometheus servers for a given project.

We now need to take this further to make the experience seamless:

1. Automatically enable Prometheus integration, configured for each deployed Prometheus instance
2. Logic to determine which Prometheus server to utilize for a given environment, if multiple clusters are connected.
3. Utilize the Kubernetes API to securely query the Prometheus servers without requiring them to be externally reachable outside the cluster

The general user flow will be:

1. User connects a Kubernetes cluster(s)
2. Deploys Helm Tiller, then Prometheus
3. At this point, Prometheus integration is now automatically enabled. Manually configuring the Prometheus URL is now disabled, instead showing that this is being automatically managed.
4. Monitoring UI elements now appear, and will function as expected for environments which have had a Prometheus server deployed.
5. In the event that the cluster for an environment does not have Prometheus deployed, they will see the empty state.

One note, the currently deployed Ingress does not have metrics enabled or proper annotations for Prometheus monitoring. This is being resolved in https://gitlab.com/gitlab-org/gitlab-ce/issues/39985.

Designs

Note: The general design and user experience for installing applications in the Cluster page is found in https://gitlab.com/gitlab-org/gitlab-ce/issues/38464

🔍 View design specs (for spacing, sizes, colors and text copying) — Hide notes in the top-right corner