Kubernetes – Infinite Space for Your Tests
summary
A case study of migrating Selenium and Jenkins CI from a home lab to Kubernetes on AWS, showing concrete metrics: running Selenium and Jenkins as Kubernetes clusters with the AWS spot fleet plugin dramatically cut compute cost (one example cites ~77× savings versus on‑demand), reduced pod startup time (~20s versus ~2min for VMs), and introduced a ~1% historical spot interruption rate with two‑minute warnings. It also reports operational limits—Jenkins masters begin to struggle around 200–250 executors—so the tradeoff is cheaper and faster test execution at the cost of added orchestration complexity and interruption handling.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:43Early company years
- 8:16Scaling compute power
- 10:23AWS cloud migration
- 14:18Spot Fleet Jenkins plugin
- 21:46Kubernetes basics
- 24:33Why Kubernetes
- 27:21Jenkins tests in Kubernetes
- 32:12Kubernetes alternatives
- 33:40Summary
related talks
43mInfinite Space for Your Tests
36mEffective Test Automation in Kubernetes
05mJenkins in the Cloud
38mUsing Containers for Continuous Integration and Continuous Delivery [I]
46mSpeed Up Regression Load with Selenoid + K8s
45mSelenium in Kubernetes: Lessons Learned
42mTesting Infrastructure in Kubernetes
35mJenkins Scaling and Organization for an Efficient CI