Out-of-the-box shared cache for Gitlab CI runners deployed in Google Kubernetes Engine
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
The current GKE integration allows me to attach a GKE cluster to my Gitlab project in several clicks, and then deploy a gitlab runners there in a couple more. That's a really cool feature.
What is missing there is a shared cache for builds, available for those runners by default.
Thanks to awesome work of @tmaczukin in gitlab-runner!968 (merged), Google Cloud Storage is now a valid storage target for cache of Gitlab runners.
So it should be totally possible (and purely awesome!) to now deploy your runners into GKE and have a GCS-backed shared cache.
This is also expected to reduce the load on Gitlab.com shared runners, since migrating to your own infrastructure will be much more approachable (no manual configuration needed).
CC @DylanGriffith, @jlenny, @danielgruesso since they were mentioned by Tomasz in the parent issue