Goal:

We're starting the productization journey with GitOps for RHOSO. We need to produce usable content upstream that will serve for early adopters as well as a base for the coming product itself.

There's a need for a curated documentation, as well as what could be the future deliverable artifacts, such as components, specific ArgoCD configuration, etc.

Acceptance Criteria:

• Repository contains only element a customer may use
• A light yet clear documentation exists and explain how to use the exposed content
• The elements are tested via our weekly pipeline when possible (ArgoCD deployment/configuration, components, etc)

Open questions:

• What's the readiness level of sathlang@redhat.com components?
  • Can we include them in the new tree, with appropriate documentation and level of warning?
• Should we keep the ArgoCD deployment playbook as a helper?
• Should we create a first "tag" before merging any changes so that we can confidently reference the tag in downstream doc to protect current consumers?