Who broke the build—Using Kuttl to improve E2E testing and release faster
summary
Teams replace fragile remote runs with Kuttl declarative test suites that run Helm installs and shell assertions on a local kind cluster, creating ephemeral namespaces, running four demo scenarios (install, split, scale, upgrade) in parallel (default eight), then tearing them down. Tests are defined in YAML testSuit/testStep/assertion CRDs, integrate into CI, produce XML/JSON reports, and cut round trips so end-to-end failures surface and get fixed locally, noticeably reducing broken builds and speeding releases.
AI-written summary · about
chapters (4)
related talks
35mWho Broke the Build? — Using Kuttl to Improve E2E Testing and Release Faster
33mWho broke the build? Using Kuttl to test and Release faster
31mWho broke the build? Use Kuttl to improve E2E tests
26mWho broke the build? Using Kuttl to release fast
27mDeclarative Testing Clusters with KUTTL
16mShift Left, Not Off a Cliff: Why Your Testing Strategy Is Breaking Developers
36mEfficient Kubernetes E2E Testing: Unleash the Power of Prow
30mTesting Kubernetes Clusters - Building Confidence in Your Changes