Jenkins in the Cloud
summary
Migration moves Jenkins onto Kubernetes using the Jenkins Kubernetes plugin and a separate build cluster that talks to dev staging and prod. A custom pod template replaces five 16GB VMs for a single pipeline, delivering reduced memory and CPU usage, but only a few pipelines are migrated so far. Problems include persistent volumes not mounting, master pods rescheduling, and runaway agents plus pod startup overhead that can negate benefits for short tasks.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:09Should I Run Jenkins
- 0:19What is Jenkins
- 0:34Jenkins at Hootsuite
- 1:00Reducing Tech Debt
- 1:20Build Kubernetes Cluster
- 1:54Jenkins doesn't know
- 2:20Jenkins is an optimist
- 2:44Losing connection to Jenkins agents
- 3:05Pod Templates
- 3:35At what cost?
- 3:50So is it worth it?
- 4:20Should you run Jenkins on Kubernetes?
related talks
38mUsing Containers for Continuous Integration and Continuous Delivery [I]
35mJenkins Scaling and Organization for an Efficient CI
39mKubernetes – Infinite Space for Your Tests
42mJenkins X, Continuous Delivery for Kubernetes
43mMoving the Unmovable: migrating from VMs to K8s
50mContinuous Deployment With Jenkins X And Kubernetes
28mWith Docker and k8's, this is not your grandparents' infra anymore!
39mAccelerate your CI/CD on Kubernetes with Jenkins X