ArgoCD Integration - Pull Model

[mikeshng]

The current OCM and ArgoCD integration is primary push model, which means the ArgoCD controller on the hub cluster needs to directly communicate with the target managed clusters. This approach does not use OCM's hub and spoke cluster post registration secured communication channel.

We are proposing implementing an ArgoCD integration pull model that leverages the OCM registration, placement and manifestwork APIs. We will introduce a new CRD call the MulticlusterApplicationSet that will evaluate cluster placements and create manifestwork wrapping ArgoCD application template to the target clusters. Once the ArgoCD application template lands on the target clusters, the ArgoCD controller will evaluate the template and deploy the application.

[mikeshng]

After discussing with the ArgoCD community. We will not introduce a new CRD.
Instead we will:

• Enhance and leverage our existing GitOpsCluster to help with importing OCM managed clusters to ArgoCD cluster inventory.
• Create a new controller that wraps Applications with ManifestWork so that the Application will be propagated to the managed cluster.

[github-actions]

This issue is stale because it has been open for 120 days with no activity. After 14 days of inactivity, it will be closed. Remove the stable label to prevent this issue from being closed.