Value Statement

The current OCM and ArgoCD integration is the 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 called 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. 

For more details, please refer to the design doc link

https://docs.google.com/document/d/1CbiIDtNy-UTo2LDSYtSJ7mGcRBBXO0suqnDwXvcwXA0/edit#heading=h.k0jw3bk45pvx

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [X] Unit/function tests have been automated and incorporated into the
  build.
• [X] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [X] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [X] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [X] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [X] The must-gather script has been updated.