Empty bar appears below Cluster Health title

Summary

(Summarize the bug encountered concisely)

There is an empty grey bar appearing just below the Cluster Health title and above the graphs.

Steps to reproduce

(How one can reproduce the issue - this is very important)

  1. Add a Kubernetes cluster (Operations > Kubernetes) into a project.
  2. Install Helm and Prometheus.
  3. Observe the Cluster Health section.

Example Project

(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)

(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)

https://gitlab.com/rpereira2/autodevops-deploy/clusters/58348

What is the current bug behavior?

(What actually happens)

A grey bar appears just below the "Cluster Health" title.

What is the expected correct behavior?

(What you should see instead)

There should not be an empty grey bar below the "Cluster Health" title.

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)

cluster_health_grey_bar

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

Results of GitLab environment info

Expand for output related to GitLab environment info 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)