Who Broke the Build? — Using Kuttl to Improve E2E Testing and Release Faster
summary
Engineers adopt Kuttl to run declarative, YAML-based end-to-end tests locally against a kind local cluster (Docker or Rancher Desktop), including Helm installs, shell test steps and assertions, with automatic namespace teardown and XML/JSON reports. Parallel execution (default eight workers) cuts a previous 1h40 CI run to under 15 minutes. Tests mirror CI operator checks, support image caching, and let developers iterate locally (amend commits) before pushing, which reduces broken-build round trips.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:04Speaker & agenda
- 1:45E2E testing challenges
- 7:54Run remote tests locally
- 9:18Kubernetes testing tools
- 10:45Kuttl as solution
- 13:14Kuttl for devs
- 17:58Kuttl live demo
- 25:27Kuttl in CI
- 27:22Parallel testing gains
- 28:27Faster Kuttl tips
- 31:16Kuttl resources
- 32:20Kuttl benefits
- 32:43Q&A
related talks
31mWho broke the build? Use Kuttl to improve E2E tests
34mWho broke the build—Using Kuttl to improve E2E testing and release faster
26mWho broke the build? Using Kuttl to release fast
33mWho broke the build? Using Kuttl to test and Release faster
27mDeclarative Testing Clusters with KUTTL
36mEfficient Kubernetes E2E Testing: Unleash the Power of Prow
28mAre You Covered? Falling in Love With E2E Testing
31mContinuous Integration Testing