Content Deep Dive

How We Rebuilt GitLab CI on GKE Spot VMs

Blog post from Speedscale

Post Details
Company
Date Published
Author
Shaun Duncan
Word Count
2,815
Company Posts That Month
14
Language
English
Hacker News Points
-
Post removed?
No
Summary

Speedscale replaced a five-year-old scheduled EC2 GitLab CI runner fleet for a 19-project Go monorepo with an ephemeral GitLab Runner deployment on GKE Standard, aiming to eliminate idle compute costs, simplify pipelines, and improve build performance. The former system relied on generated child pipelines, per-job Docker-in-Docker builders, artifact-based caches, repeated tool installation, and a large shared build image, while the new design uses Spot-based job pools that scale to zero, a small on-demand system node for runner availability, and a dedicated persistent BuildKit service with shared layer caching. To address unreliable Spot capacity, the cluster supports several Spot machine families and zones plus a zero-minimum on-demand fallback pool, while admission limits and retry policies reduce excessive pending jobs and manage preemption. The migration also introduced Artifact Registry for Go module proxying and mirrored container base images, GCS-backed remote Go build caching through GOCACHEPROG and gobuildcache, and BuildKit-based CGO cross-compilation using xx, reducing repeated QEMU setup and unnecessary toolchains. The author notes that Cloud NAT egress costs motivated registry mirroring, and describes rebuilding the platform rather than incrementally preserving old assumptions, with AI assistance used to develop the system but production experience driving subsequent corrections.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Kubernetes 1 5,136 499 114 +17%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.