Quality in a Square K8s-native Quality Assurance of Microservices w. Testkube
summary
Claim: move integration, performance and security tests out of huge CI pipelines and run them natively on the cluster, triggered by cluster events or GitOps. Demo uses Testkube CRDs (test, testSuite, testTrigger), executors that run as Kubernetes jobs (K6, Postman, Maven/Gradle, Zap) and Flux/Argo for GitOps; results land in MongoDB/NATS. Proof: local demo and a five‑node GCP cluster run scheduled tests (every five minutes) and event‑driven suites, and missing executors are added in about one to two days.
AI-written summary · about
chapters (13)
- 0:00Quality in microservices
- 1:06Monolith to microservices testing
- 3:53Speaker's microservices journey
- 5:00Continuous delivery benefits
- 8:50ISO 25010 quality attributes
- 16:18Monolithic CI/CD problems
- 19:25Event-driven testing future
- 23:37Digital product assembly line
- 26:25Testkube and GitOps
- 31:01Testkube architecture
- 35:15Live Testkube demo
- 45:19Holistic quality monitoring
- 49:31Q&A
related talks
45mMario Leander Reimer: K8s-native Quality Assurance of Microservices with Testkube
16mWhy Kubernetes Applications Require a New Approach to Testing using Testkube- 16mWhy Kubernetes Applications Require a New Approach to Testing using Testkube
24mWhy Kubernetes Applications Require a New Approach to Testing using Testkube
33mThe Power of a Unified Testing Approach in Kubernetes
33mTake Your Tests to the Cloud with Testkube
50mContinuous API Mocking and Testing with Microcks, Keptn, and Testkube
32mRedefining Continuous Testing in Kubernetes Environments