Simplifying Service Mesh Operations with Flux and Flagger
summary
Service mesh upgrades are automated using GitOps: Flux + Flagger automate control- and data-plane upgrades by opening pull requests when a new Istio version appears, running Kind-based end-to-end tests and analyzers, then reconciling the cluster. The presenters show a live workflow where Flux self-upgrades, a control-plane PR applies, a follow-up PR updates injected sidecars, and a canary moves 5% of traffic to the new proxy while Prometheus gates rollout. Bad configs block via analyzers; revision-based upgrades are noted as pending.
AI-written summary · about
chapters (5)
- 0:00Start
- 5:40CNCF Flux Project
- 8:29Flagger - Progressive Delivery
- 28:16Advantages Disadvantages
- 28:56Future Workflow
related talks
15mLightning Talk: GitOps and Progressive Delivery with Flagger, Istio and Flux
27mGitOps Evolution Through the Lens of a Flux Maintainer
27mLeveraging Service Meshes for A/B, Blue-Green, and Canary Deployments (aka "Progressi...
33mProgressive Delivery Techniques with Flagger
33mFlux Ecosystem Evolution
42mIntro: Flux
39mEnhance Your Kubernetes Experience with GitOps & Flux
10mCNCF Project Update: Flux
