// the find
stefanprodan/gitops-istio
A GitOps recipe for Progressive Delivery with Flux v2, Flagger and Istio
A workshop-style reference implementation showing how to wire together Flux v2, Flagger, and Istio for progressive delivery on Kubernetes. It covers canary releases and A/B testing with automatic rollback driven by Istio metrics. The target audience is platform engineers who want a working starting point rather than reading four different projects' docs separately.
The dependency ordering between Istio and app Kustomizations is done correctly — a common stumbling block that trips up most first-time Flux+Istio setups. The automated Istio version bump via GitHub Actions opening PRs is genuinely useful and not something you'd think to set up yourself. The rollback example using real error-rate and latency thresholds from Prometheus is concrete and testable, not just theoretical. The e2e CI on Kind means the main path actually gets validated.
This is a workshop repo, not a production template — it uses Kubernetes v1.20 as the minimum, which is years out of support and signals how stale the baseline is despite recent pushes. There's no multi-tenancy, RBAC, or network policy example, so teams that need more than a single shared namespace will have to figure that out themselves. The A/B testing match conditions target Firefox by User-Agent, which is a toy example that doesn't translate to real session-based targeting without significant rework. No secrets management — the bootstrap assumes you're fine with Flux SSH keys and nothing sensitive beyond that.