Switch from shared CI runners to Kubernetes cluster instances for GitLab.com
Problem to solve
We currently use Digital Ocean droplets for our shared runners on GitLab.com. These are great for CI, but we want to be able to offer the advantages of Auto DevOps (https://docs.gitlab.com/ee/topics/autodevops/) out of the box for GitLab.com customers.
We can remove a lot of configuration for customers if we're able to offer a Kubernetes cluster as part of our plans.
To be discussed.
What does success look like, and how can we measure that?
- GitLab CI jobs for GitLab.com groups are now executed on Kubernetes clusters.