Is Argo CD or Flux more widely used, and is switching worth it?

November 17, 2026 5 answers
Asked by 9j+orbitcaper_473

I'm most of the way through migrating from Argo CD to Flux, and troubleshooting the setup has been harder than expected. Which one is more common in industry, and is it worth finishing the switch if I didn't have a strong reason to make it?

Answers

p.764!quorvex

Both show up in production, but I wouldn't treat a handful of workplace examples as an industry survey. Argo CD appears to have more public project activity, though stars and releases aren't a reliable count of actual deployments.

For learning, either is useful. Knowing how reconciliation, Git configuration and Kubernetes resources fit together will transfer better than betting everything on which tool is most popular.

Reply to this answer
8g~parcelferrule_562

Argo CD's UI is a real advantage when developers or customers need to see what's deployed and spot trouble without digging through cluster resources. ApplicationSets and generators are also appealing when you're managing lots of similar applications across clusters.

If the team already relies on that visibility and Argo CD was working, I'd want a concrete benefit before replacing it.

Reply to this answer
7x!plovergizmo_452

Flux is a reasonable choice if your team is comfortable troubleshooting through Kubernetes tools rather than relying on a GitOps UI. It can work well for platform level resources, but make sure people can see reconciliation failures and have access to investigate them.

Without that visibility, a chart update can feel like a guessing game. I'd sort out logs, alerts and permissions before calling the migration done.

Reply to this answer
_n49+claygrommet.7

You don't necessarily have to pick one for every job. Flux could manage platform resources while Argo CD handles applications that need a developer facing view. Just make ownership explicit so both controllers aren't trying to reconcile the same resources.

9j+orbitcaper_473:

So running both in one cluster can be an option, as long as they have separate responsibilities?

_m38+ferrulegizmo.6:

Right. Define which tool owns each set of resources and check for overlap before enabling reconciliation.

Reply to this answer
v.846!corkladle

Being most of the way through doesn't mean you have to finish. If this started as an experiment, compare the remaining work and the cost of going back with what Flux actually gives you. A working Argo CD setup is a perfectly good place to stop if there's no clear payoff.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions