Unblocking the Release Train with Istio Traffic Management
summary
Wealth Wizards routes HTTP traffic to branch deployments using Istio destination rules and virtual services that match a prefixed hostname or an X-Variant-ID header, injecting that header at the ingress and routing to subset-labeled pods. Automation (an auto-kube generator plus a kube-housekeeper cleanup job) and a small Node library (edge-propagate) ensure headers are propagated and variants are created/removed. Result: compliance and QA test isolated branches, merges reach production in hours not days; initial control-plane scaling issues are resolved.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 2:50Services
- 4:57Platform evolution
- 6:58Slowmoving industry
- 8:11Pipeline
- 8:44Compliance Check
- 9:24Feature Flags
- 11:15Environments
- 11:37Microservices
- 12:13Ecco
- 13:21SEO
- 13:57HTTP headers
- 16:32Destination rule
- 17:10Virtual service
- 18:39Mesh virtual service
- 19:03How was this managed
- 19:44Cube housekeeper
- 20:06AutoCube
- 20:51Edge Propagation
- 23:23Propagation Idea
- 23:55Gains
- 25:24Learning curve
- 28:22Thank you
- 28:43Questions
related talks
24mRunning Istio in Production as a Small Team of Newbies
43mProgressive Application Delivery: Istio Ambient Mesh and Argo Rollout in Action
38mGitOps for Istio - Manage Istio Config like Code
24mNavigating the Maze of Multi-Cluster Istio: Lessons Learned at Scale
43mUsing Kubernetes, Spinnaker and Istio to Manage a Multi-cloud Environment
37mZero-downtime Deployment Strategies (...) [ENG]
32mRoll Out the Red Carpet for Production Kubernetes Clusters with a Kube-vip
44mA Guided Tour of ISTIO Ambient Mesh