clarify how/if to integrate ArgoCDAgent

[ch-stark]

How does the ArgoCD Agent relate to ACM Policies?

happy to discuss and help with any decision.

This will be asked by customers quite certain

[ch-stark]

see here how ACM ArgoCD Pull-Model versus Agent can be compared

https://github.com/open-cluster-management-io/argocd-pull-integration?tab=readme-ov-file#comparison-basic-vs-advanced

[mikeshng]

The argocd-agent is intended for advanced use cases where users need additional capabilities.

Using ACM Policy to propagate Argo CD Applications is easier to set up, more intuitive, and should remain the default approach. It involves fewer moving parts, reduces the chance of failures, and is easier to understand.

Only when users need additional capabilities, such as using the Argo CD UI to display Apps, should we introduce them to the argocd-agent mode.

[bcarr-rh]

Should we add this as a feature that can be turned on? Currently we support ArgoCD Push Mode for applications and then ArgoCD deployed to each cluster and applications can either use policies or be deployed locally on each cluster depending on the customer

[mikeshng]

Should we add this as a feature that can be turned on?

Yes, we should.

Once the ACM gitops-addon's argocd-agent integration reaches GA (targetting ACM 2.17), we should consider making it the primary/default multicluster gitops pattern. CC @berenss