OCP/Telco Definition of Done
<https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde>
Epic Template descriptions and documentation.
<https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit>
ACM-wide Product Requirements (Top-level Epics)
<https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit>

*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*

Epic Goal

Multicluster Global Hub Operator needs Kafka and PostgreSQL to function. In the Tech Preview they have been added as sample scripts. In GA version we need to make it fully supported. If Red Hat is recommending operators, it has to be fully supported. However, there are different ways by which this dependency can be packaged. We have to figure out which way we want to tackle this. 

Different options are listed here: https://docs.google.com/presentation/d/1DP6XDsOg_icxtIHtDkar_0SN-5ROyT0r3QUkJ-jtlvk/edit#slide=id.g2755c96e638_0_0

Why is this important?

The approach must factor in several things. They are listed here, but not in order - 

1. What makes it most easy for the customer
2. What can make supporting Bring Your own scenario easier
3. How does it fit into RH supported scenarios
4. How easy does this make middleware updates to be possible - DB or Kafka version
5. How easy does this make data backups possible
6. How easy is it to tune and manage middleware configurations

Scenarios

Acceptance Criteria

This issue has been raised by one of our key customers in the Financial domain. The solution will have to be signed off by them

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. Our customers have asked to look at how Ansible, ACS, Service Mesh operators handle this. There does not seem to be one uniform approach on this in RH: https://redhat-internal.slack.com/archives/C03A998ETHR/p1692589969264689?thread_ts=1692237582.254029&cid=C03A998ETHR

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 - Downstream documentation merged: <link to meaningful PR>