Microservices, Service Mesh, and CI/CD Pipelines: Making It All Work Together [I]
summary
Live demo builds a MicroSmack app with a Brigade-driven pipeline that builds a Go image, pushes to ACR, and runs Helm to update Istio/Envoy sidecars so traffic can be split for per-service canaries. Grafana/Prometheus show latency spikes when 90% of traffic hits the canary, the code change (color → “Chuck Norris”) fixes the regression, Kashti surfaces build logs, and merging flips Helm route rules to 100% traffic to prod.
AI-written summary · about
chapters (10)
- 0:00Introduction to service mesh
- 2:58CI/CD and canary testing
- 5:02Microservices testing challenges
- 8:09Istio service mesh overview
- 11:46Brigade event-driven scripting
- 15:52Demo application setup
- 19:37Canary deployment demo
- 24:05Debugging with Istio and Brigade
- 27:27Finalizing the deployment
- 29:40Conclusion and Q&A
related talks
34mSupercharge Your Microservices CI/CD with Service Mesh and Kubernetes
56mHow to get a grip on your microservices system using a service-mesh
51mHow to get a grip on your microservices system using a service mesh
52mEmpower Your Microservices with Istio Service Mesh
01h 01mIstio Service Mesh & pragmatic microservices architecture
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
54mEasy Microservices with Kubernetes and Istio
52mMaking microservices micro with Istio Service Mesh & Kubernetes