compare
Argo Rollouts vs Flagger
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Argo Rollouts | Flagger |
|---|---|---|
| Language | Go | Go |
| Licence | Apache-2.0 | Apache-2.0 |
| Stars | 3.6k | 5.4k |
| Latest | v1.10.0 | v1.45.0 |
| Last push | 2026-10-06 | 2026-09-21 |
| Release cadence | about 41 days between releases | about 139 days between releases |
| Active contributors | 37 commit authors on the default branch in the last 90 days | 4 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Flagger replaces Argo Rollouts. Alternatives to Argo Rollouts →
Full replacementCanary, A/B and blue-green releases driven by metrics, on top of standard Deployments and a service mesh or ingress.
Argo Rollouts
- v1.10.02026-08-27guard empty Values in injected anti-affinity check (cherry-pick #4832 for 1.10) (#4917)
- v1.9.12026-07-17Minor security release to address CVE-2026-35469
- v1.10.0-rc12026-07-03skip full CI for documentation only changes (#4737)pre-release
- v1.9.02026-03-20deps: update debian11 to debian12 (#4652)
- v1.8.42026-02-13fix: bluegreen analysis prematurely succeeds if new ReplicaSet becomes unsaturated by @jessesuen in
Argo Rollouts
✓ signed The latest release, v1.10.0, carries a signature GitHub verified.
Loading the security report
Flagger
✓ signed The latest release, v1.45.0, carries a signature GitHub verified.
Loading the security report