41 ms·
ArgoCD is not synonymous with GitOps (for Kube or in general) nor do they have a monopoly on effective implementation thereof. I certainly prefer FluxCD, mysel
by mtndew4brkfst 2y ago
ArgoCD is not synonymous with GitOps (for Kube or in general) nor do they have a monopoly on effective implementation thereof.
I certainly prefer FluxCD, myself.
- hadlock 2y agoI've used both in production. FluxCD is fully batteries-included, but the UI (3rd party!) leaves a lot to be desired, and turns off a lot of developers, and as a result makes it difficult to get team buy-in ArgoCD is missing some critical systems, like how to tell when the underlying image needs updating. There are a number of ways to handle this but it's either a kludge, a plugin, or both. However, the UI is fantastic and very easy to pickup and understand, team buy-in is usually close to 100% I generally recommend starting with argo, and once the team/project/s have matured, migrate to FluxCD. Eventually you want to lock everyone out of the CD system, but initially people are skeptical and want to understand/watch everything work, especially during debug.