This message was deleted.

Hi @average-forest-16300 The biggest difference between them is the scale. If you want to apply GitOps over, let's say, more than 10 clusters, then you should start by looking at Fleet. Fleet works using pull model and benefits for the agent running on the downstream clusters to take care of that. It also manages bundles in a binary format to optimize the distribution or artifacts. Theoretically it can scale up to a million clusters, but let's say that is well tested and proven to work over tens of thousands clusters. On the other side ArgoCD follows a push model that may be very slow so it works great for typical dev>test>prod smaller scenarios or, as I said, when the number of clusters to target for deployments is not big. A good feature of ArgoCD is a cool ui to model deployments so you can easily model complex scenarios very quick. Fleet has a quite powerful targeting syntax (to be able to deal with all the challenges created by scale, where targeting needs a lot of fine tuning and proper handling of exception/special cases) but the UI is quite basic. In any case they are non mutually exclusive and both can live in the same scenario. As you use Rancher, Fleet is just there ready to be used as Rancher itself uses it for the downstream clusters management. ArgoCD is available on Rancher's catalog so not a big deal to have it up and running. Hope it helps.

thanks