In the 2.15 release, the ACM gitops-addon will be able to install the argocd operator on managed/spoke cluster and optionally deploys the argocd-agent's agent components on the same managed/spoke cluster. In other words, the ACM gitops-addon handles the full ordering: operator then ArgoCD CR (lays down argocd core components) then argocd-agent's agent (when enabled). This ensures the agent lands only after its prereqs exist and the local argocd is in place to provide the expected prereqs to the agent component.

In this Jira, the ACM team is going to contribute upstream changes to the argocd-operator so it can also deploy argocd-agent's agent component, not just the principal. This is necessary because the GitOps operator already reconciles the ArgoCD CR that lays down Argo CD itself (and principal components). If a user enable agent mode, the same operator path should lay down the agent too. This removes the custom agent installation logic from the ACM gitops-addon and maintenance in ACM and it formalizes a shared upstreamed capability. The end result is a simpler fleet story for users, tighter lifecycle management in one operator, and another deeper collaboration between the ACM and GitOps teams.