Crap, ArgoCD is much much more powerful than I thought it was, and I might end up using it instead of Flux now that I'm much less memory-constrained.
I'll find a way not to throw away all that writing I did for a Flux-based cluster anyway 馃槃
Discussion
Loading...
@thibaultamartin Are you switching because of a certain feature, that flux doesn't have?
@koyax I've played with Flux and I really liked that Flux was very low overhead. But I've also found Flux to sometimes be a bit difficult to understand (e.g. I have a draft about Flux Kustomizations vs kubernetes kustomizations).
ArgoCD also seems to have a lot more traction in the industry, and a brighter (better funded) future than Flux.
Flux remains a very interesting tool, and I'm happy both projects exist :)
@thibaultamartin @koyax so, if I understand correctly, you're not saying ArgoCD is more powerful than FluxCD?
Presumably, you used to believe argo was less powerful than flux but now you've learned that's not the case and you want to adopt it because you see it's being favoured by big players in the industry (I think it's supported on platforms like OpenShift) and you think it's a safe bet career-wise.
I can definitely understand that position, do what you gotta to futureproof your skills 馃憤
I actually took the opposite approach. We use argo at work so I went out of my way to use flux for my homelab so that I could better understand the pros and cons 馃槀
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled