Inside Kraken: Regression Testing With Traffic Replay
Blog post from Speedscale
Kraken is Speedscale’s internal Kubernetes-based release-validation system, designed to test candidate components together by capturing, analyzing, mocking, and replaying real application traffic before promotion. It addresses integration failures that unit tests may miss, such as missing EndpointSlice permissions that left replays stuck initializing or an operator startup failure caused by an absent optional Argo Rollouts resource. Kraken combines release manifests, workloads, recorded traffic, fixtures, configurations, and validation scripts in GitLab CI, using recorded dependency responses to make regressions repeatable while retaining real operators, applications, responders, generators, and analysis services under test. Its suite includes committed fixtures for stable known scenarios and live capture tests for current protocol and pipeline behavior, with careful review required when updating recordings, transforms, assertions, or expected behavior. Validators inspect meaningful evidence such as replay reports, response matches, metadata, configured goals, and deliberate expected failures rather than treating command completion as success. The system has also exposed coverage weaknesses, including a chaos replay that passed without applying chaos because no dependency interactions existed, reinforcing the need to verify that successful tests actually exercise their intended behavior.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Kubernetes | 4 | 5,167 | 507 | 114 | +18% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.