Who broke the build? Using Kuttl to test and Release faster
summary
Team replaces slow remote CI e2e runs with Kuttl to reproduce production-like Kubernetes environments locally, spinning up a kind cluster per test namespace and running 4 parallel tests (default supports 8) against Artifactory installs, scale and upgrade flows. Tests use YAML declarative suites and shell steps, enforce a 900s timeout, emit XML/JSON reports, and all four demo tests pass — result: far fewer broken builds and much shorter fix round trips.
AI-written summary · about
chapters (8)
- 0:00Introduction and agenda
- 4:28Ideal development environment
- 9:22Introducing Kuttl
- 12:55Installing Kuttl
- 18:29Demo and test structure
- 26:47Kuttl documentation
- 29:45Summary and benefits
- 30:29Q&A session
related talks
26mWho broke the build? Using Kuttl to release fast
34mWho broke the build—Using Kuttl to improve E2E testing and release faster
35mWho Broke the Build? — Using Kuttl to Improve E2E Testing and Release Faster
31mWho broke the build? Use Kuttl to improve E2E tests
27mDeclarative Testing Clusters with KUTTL
31mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests
30mTesting Kubernetes Clusters - Building Confidence in Your Changes
36mEfficient Kubernetes E2E Testing: Unleash the Power of Prow