Error initializing Kubernetes cluster does not provide adequate error message in gitlab

I used google SSO to login and setup my kubernetes cluster. I used the default settings and it seemed to stall on the creation page when I view on gitlab.com. After logging into GCP, I noticed that there was an error. We should do a better job relaying that info to gitlab so that the user doesn't have to context switch.

Screen_Shot_2019-03-25_at_2.16.40_PM Screen_Shot_2019-03-25_at_2.17.01_PM

Proposal

Show more detailed loading state of cluster creation within GitLab. GCP shows:

Screen_Shot_2019-03-25_at_2.32.52_PM

This includes displaying errors returned from GCP, such as running out of IP.

Edited Mar 25, 2019 by Taurie Davis
Assignee Loading
Time tracking Loading