Who broke the build? Using Kuttl to release fast
summary
Claim: running Kubernetes end-to-end tests locally with Kuttl cuts CI round trips and reduces broken builds. The demo boots a kind cluster on Docker Desktop, runs two parallel test steps that install Artifactory via Helm (700 MB image), asserts replica counts, then tears down namespaces; the run takes about six minutes locally. Kuttl integrates with CI, supports up to eight concurrent tests, and works with kubectl, Helm and K9s—proof of concept succeeds and prevents slow remote fail-fix cycles.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:03JFrog mission
- 2:30Software release cycles
- 3:54Dev environment setup
- 6:04Feature branch problems
- 8:55Introducing Kuttl
- 10:00How Kuttl works
- 13:55Kuttl test structure
- 14:41Live demo
- 20:45Kuttl benefits
- 21:51Summary and Q&A
related talks
33mWho broke the build? Using Kuttl to test and Release faster
35mWho Broke the Build? — Using Kuttl to Improve E2E Testing and Release Faster
34mWho broke the build—Using Kuttl to improve E2E testing and release faster
31mWho broke the build? Use Kuttl to improve E2E tests
36mSuccessful Kubernetes Development Workflows
27mDeclarative Testing Clusters with KUTTL
13mInterview of Jerome Petazzoni
32mKubernetes: Pimp My Laptop