4 ms·

Argo, flux, fleet, gitlab pull based…. Does anyone have recommendations for a good comparison blog post?

nickjj 4y ago
I don't have anything written up but I extensively compared Argo CD vs Flux about 6 months ago and chose Argo CD in the end. I'm really happy with it and currently deploy multiple services to multiple environments (different AWS accounts for each env) in a way that works for multiple teams being able to deploy releases on their own. I only use it in a pretty basic way for now (Argo CD + Pre/Post sync hooks + Notifications) but I'm starting to look into using Argo Events + Workflows. I feel like Argo CD pulls everything together as a cohesive framework for deploying workloads into Kubernetes, plus there's a built in web UI that's nice to give read-only access to developers so they can see details about their workloads without needing cluster access with kubectl.
- coopreme 4y ago
  Thanks for the thoughts. Looking at solutions to help with state drift in multi-tenant clusters. Using lots of rancher but a dev “flipping switches” sometimes creates pain for me. Argo seemed to be a good solution to “no more kubectl in prod” but I think there is some neato fleet integration with Rancher. Thanks again!!
longcommonname 4y ago
The biggest difference between the two is how it runs. If you have many clusters then you get to chose between many or one argocd instance. We run a few argo instances that manage many clusters. If you use flux, all of cluster needs to have access to github. If you run argo you can restrict it so that the argo cluster (which manages many others) only needs access. You still have to have argo get access to the child clusters. I prefer the simplicity of flux, I like the read only ui of argo. The thing I really don't like about argocd is that you have to give the parent cluster admin to every cluster it manages. If you use git webooks you've now had to expose your controller that can manage your fleet to the public. Argocd also randomly has really bad bugs show up. Like completely ignoring appsets. Or pathological syncing cases.
nagyv 4y ago
I have seen a series of reviews from Giant Swarm. Example: https://www.giantswarm.io/blog/gitops-with-gitlab-agent-for-kubernetes-giant-swarm https://www.giantswarm.io/blog/gitops-with-gitlab-agent-for-...

I don't have anything written up but I extensively compared Argo CD vs Flux about 6 months ago and chose Argo CD in the end. I'm really happy with it and currently deploy multiple services to multiple environments (different AWS accounts for each env) in a way that works for multiple teams being able to deploy releases on their own. I only use it in a pretty basic way for now (Argo CD + Pre/Post sync hooks + Notifications) but I'm starting to look into using Argo Events + Workflows. I feel like Argo CD pulls everything together as a cohesive framework for deploying workloads into Kubernetes, plus there's a built in web UI that's nice to give read-only access to developers so they can see details about their workloads without needing cluster access with kubectl.

coopreme 4y ago
Thanks for the thoughts. Looking at solutions to help with state drift in multi-tenant clusters. Using lots of rancher but a dev “flipping switches” sometimes creates pain for me. Argo seemed to be a good solution to “no more kubectl in prod” but I think there is some neato fleet integration with Rancher. Thanks again!!

longcommonname 4y ago

The biggest difference between the two is how it runs. If you have many clusters then you get to chose between many or one argocd instance. We run a few argo instances that manage many clusters. If you use flux, all of cluster needs to have access to github. If you run argo you can restrict it so that the argo cluster (which manages many others) only needs access. You still have to have argo get access to the child clusters. I prefer the simplicity of flux, I like the read only ui of argo. The thing I really don't like about argocd is that you have to give the parent cluster admin to every cluster it manages. If you use git webooks you've now had to expose your controller that can manage your fleet to the public. Argocd also randomly has really bad bugs show up. Like completely ignoring appsets. Or pathological syncing cases.

nagyv 4y ago

I have seen a series of reviews from Giant Swarm. Example: https://www.giantswarm.io/blog/gitops-with-gitlab-agent-for-kubernetes-giant-swarm https://www.giantswarm.io/blog/gitops-with-gitlab-agent-for-...