I'm relatively new to ArgoCD, coming from a background in Flux. I expected them to be quite similar, but I'm hitting some unexpected issues:
1. It seems that Kustomize ConfigMap or Secret generators aren't supported.
2. I couldn't locate a command or button in the UI to resynchronize the repository state.
3. SOPS isn't natively supported, which means I have to use SealedSecrets instead.
4. Configuring Applications feels quite complex, especially with overlays that require specific placement in the repository to add basic values.yaml files.
Are these just limitations I've overlooked, or are they common issues?
4 Answers
For the resync issue, just hit the "Refresh" button on the app instead of looking for something for the repository. It might seem tricky at first, but it does what you need!
Honestly, I've found ArgoCD to be a bit of a pain compared to Flux. Sure, it has some cool features like app state management, but the complexity it adds can be frustrating.
About the Kustomize issue, we’ve had success with the **configMapGenerator** in our kustomization.yaml when deploying with ArgoCD, so they do work at least to some extent!
ArgoCD and FluxCD do have their differences! Some people find Argo's UI and features like Argo Rollouts really useful. It sounds like you might get more out of it with ApplicationSets using different Generators if you dig into that.
Yeah, Flux just launched a web UI too, so both tools are evolving!
Thanks for clarifying that! Refreshing the app instead of the repository makes total sense!