Feature Overview

This feature should work with All Patterns of RHACM (Push, Pull, Agentmode, Addon)

...
This is described in the offical doc
Argo CD supports managing ApplicationSet resources in namespaces other than the control plane's namespace
Argo CD administrators can define a certain set of namespaces where ApplicationSet resources may be created, updated and reconciled in.

As Applications generated by an ApplicationSet are generated in the same namespace as the ApplicationSet itself, this works in combination with App in any namespace.
This is the natural enhancement on the hub.
So our ArgoCD plus model will be beneficial for sure
For pull model, this would be helpful too. It seems the following:

create multiple appsets in different namespaces on the hub, It seems our pull model can support the following case with some enhacements
ns1/appset1 ===> generates ns1/app1 for each cluster
ns2/appset2 ===> generates ns2/app1 for each cluster
...
nsN/appsetN ===> generates nsN/appN for each cluster
Then on each cluster, there are multiple apps deployed (ns1/app1, ns2/app2, ... nsN/appN)
use gitps addon to deploy gitops openshift instances to ns1, ns2 ... nsN on each cluster

Goals

Gitops already supports a Technical-preview: GITOPS-3754

• …

Requirements

This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.

(Optional) Use Cases

This Section:

• Main success scenarios - high-level user stories
• Alternate flow/scenarios - high-level user stories
• ...

Questions to answer

• ...

Out of Scope

• …

Background, and strategic fit

This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?

Assumptions

• ...

Customer Considerations

• ...

Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this
  product feature? For users/admins? Other functions (security officers, etc)?
• Does this feature have a doc impact?
• New Content, Updates to existing content, Release Note, or No Doc Impact
• If unsure and no Technical Writer is available, please contact Content
  Strategy.
• What concepts do customers need to understand to be successful in
  [action]?
• How do we expect customers will use the feature? For what purpose(s)?
• What reference material might a customer want/need to complete [action]?
• Is there source material that can be used as reference for the Technical
  Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or
  Release Note)?