Hey everyone, I'm diving into local deployment and I'm a bit torn between using ArgoCD and Flux. I feel like ArgoCD has more features, but I'm struggling with how to manage sources properly. Currently, one of my sources is linked to a Helm chart that installs an application with my manifests, specifically for setups like ESO, the Ingress Controller, and Argo where I'm utilizing Terragrunt modules. I'm curious about how others are using ArgoCD, and if you could share any examples that might help clarify things for me. Also, I've been using a common base and kustomization strategy for Flux, but I'm starting to wonder if that's the best approach with ArgoCD.
1 Answer
Honestly, I prefer Flux because it’s straightforward and works well with native Helm. ArgoCD is useful if you want a UI and resource visibility, but I haven't explored its complex features much. I primarily work with Helm charts, and I’ve encountered quite a few issues using ArgoCD with them.
What kind of issues have you faced with ArgoCD?