Epic Goal

OCM offers a very refined set of features intended to allow multicluster users to plug in and enhance the foundational offering with the tools they prefer to use or know best. 

However, for many users who are new to multicluster it can be challenging to do this on their own. 

To assist, we propose to offer an opinionated view to build a more "advanced" multicluster solution utilising OCM including:

• observability with Thanos and Prometheus (or?)
• application deployment from Argo
• a basic, read only UI to make visualising the clusters easier

With these steps (or scripts) an OCM installation with key components can easily be created and utilised. This would help our users get a base deployment working and begun contributing to OCM.

Additionally, this allows OCM to outline to the Multicluster community our viewpoint and to easily demonstrate and share key concepts with the community leadership.

Finally, by doing this we don't compromise the integrity of the simplicity and extensibility of the core OCM offering; users can still extend as they prefer or use our opinionated scripts and runbook.

Why is this important?

As above - also, from a RHACM standpoint we are hearing more and more that customers want to work with OCM but are blocked when they need to create a RHACM-like experience with basic services such as observability, application management, and UX via a UI.

Our RHACM customers are often managing unique and complex environments and their knowledge about how to do that is useful to share into the OCM and Multicluster community. 

This also allows us to streamline real world features we see downstream into community and upstream features leading to multicluster thought leadership and usability.

Scenarios

Accelerate onboarding of existing RHACM customers experiences to contribute to OCM.

Enable users to use OCM with expected supplemental services.

Acceptance Criteria

A simple document and/or set of steps/scripts to build OCM with key components.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. How would this relate to Stolostron? Would we look at making this a helm chart to build something similar?

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.
• Considerations were made for Extended Update Support (EUS)