3 ms·
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 curren
by 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 agoThanks 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!!