Epic Goal

...

Install
https://issues.redhat.com/browse/SECFLOWOTL-89
for use of ArgoCD-Pullmodel

Document the precedure

currently in our ArgoCD pull model, we don't limit the ways to install ArgoCD instance on managed clusters. So customers can do whatever they like. Here is what we recommend
https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/gitops/gitops-overview#gitops-[…]enerator
We may still leverage policy to deliver the new yamls to managed clusters for installing the small footprint gitops

Why is this important?

...

Scenarios

...

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.