Dynamically Testing Individual Microservice Releases In Production
summary
Claim: deploy candidate pods into production and run realistic end‑to‑end tests without exposing users by using Istio to route only test traffic via an override header; an operator that emits VS/DR auto‑generates the needed VirtualService and DestinationRule per service/version so configs don’t explode. Implementation uses Envoy/Istio, must regex‑match collapsed header values, requires namespace isolation and header trust, and pairs with Flagger for real rollouts. Prototype exists as CLI+operator; demo hits Docker Hub issues but v0.2 is reported working.
AI-written summary · about
chapters (7)
- 0:00Start
- 4:51Service Taxonomy
- 6:38Testing new versions
- 8:41Integration tests
- 12:52Service mesh
- 20:35Repeated header key
- 32:28V2 database shim
related talks
52mEmpower Your Microservices with Istio Service Mesh
52mMaking microservices micro with Istio Service Mesh & Kubernetes
50mDeveloping Microservices with Istio
58mService Mesh and Sidecars with Istio and Envoy
47mDev/Testing challenges with microservices and CD
38mStop Reinventing the Wheel with Istio
01h 01mIstio Service Mesh & pragmatic microservices architecture
50mMaking Microservices Micro with Istio & Kubernetes
