GitLab + Nomad: A GitOps Dream — How the Internet Archive Migrated from Kubernetes to Nomad & Consul
summary
The Internet Archive replaces Kubernetes with HashiCorp Nomad + Consul, using GitLab’s existing build phase and a simpler custom deploy phase that injects CI vars into a templated project.hcl. Deployment requires a 2-line .gitlab-ci.yml and two CI/CD variables (eg. NOMAD_TOKEN), so repos deploy in minutes. The stack uses Nomad, Consul, Fabio for edge routing, Docker images and HCL v2; developers get hot copy on save into running containers. Result: over 100 deployments migrated and pipelines run roughly twice as fast.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker intro
- 1:29Why switch from Kubernetes to Nomad
- 3:56Nomad and Consul stack overview
- 7:29GitLab CI/CD integration with Nomad
- 9:12Quick setup for GitLab and Nomad
- 12:43Minimal Nomad project example
- 16:13Review apps and Nomad status
- 19:02Networking and Docker login tips
- 20:48Nomad UI and monitoring
- 21:32Useful aliases and hot reload
- 22:58Handling large repositories
- 24:47GitLab runner optimizations
- 25:30Resources for Nomad setup
- 26:13Results after one year
- 28:16Migration timeline and Q&A
related talks
23mNomad the Easy Way - Creating GitHub & GitLab Pipelines in Minutes
41mFrom Traditional to GitOps: A Tale of Modernizing Two Goverment Institutions in One Year
33mAbstracting Nomad: Patterns for Deploying to Nomad at Scale- 41mFrom Traditional to GitOps: A Tale of Modernizing Two Goverment Institutions in One Year
02h 47mPipes on Pipelines
32mEnhance Your Kubernetes CI/CD Pipelines With Open Source
30mA beginner's journey: Scaling self-hosted platform infrastructure with Nomad
44mNomad, orchestration made in HashiCorp