Kubernetes Native Continuous Deployment with FluxCD, Flagger, and Linkerd
summary
StackPulse describes a Kubernetes-native CD pipeline that wires FluxCD, Flagger, Linkerd together to run frequent canary rollouts: CircleCI builds images to Google Container Registry, Flux detects new images and Git changes, Flagger increments traffic (10%→+5–10% steps) while scraping Prometheus metrics and Linkerd provides per-pod splits; failures trigger instant rollback to zero canary replicas. The pipeline adds webhooks for pre/post rollout tests and uses feature flags (flipt) to disable faulty code without full rollbacks.
AI-written summary · about
chapters (8)
- 0:00Introduction to talk
- 1:29Business need for CD
- 3:35Canary deployment strategy
- 13:50FluxCD deep dive
- 24:10Flagger progressive delivery
- 31:02Service mesh role in CD
- 37:48Feature flags and dark launching
- 42:50Key takeaways summary
related talks
16mProgressive Delivery with Flagger
33mProgressive Delivery Techniques with Flagger
43mCloud-Native Progressive Delivery
34mSupercharge Your Microservices CI/CD with Service Mesh and Kubernetes
21mIntroduction to FluxCD
15mLightning Talk: GitOps and Progressive Delivery with Flagger, Istio and Flux
40mTreating Kubernetes as a Linux Distro: APT-Style Packaging with FluxCD
32mCloud Native Progressive Delivery
