Epic Goal

Finalize the solution how to provide the middleware in the initial GA version.

Why is this important

Currently, we have sample scripts to deploy kafka and postgres. It maybe not sufficient for GA release.

Scenarios

Kafka and Postgres dependencies (Pros/Cons)

1. 1. BYO-Kafka and BYO-Postgres support (standard mode and container mode)
      1. Minimal requirements (bring topic/user only or need the whole Kakfa)
      2. How to upgrade the middleware
      3. How to scale the middleware
      4. How to manage the middleware
   2. Continue to use sample scripts to install
      1. Strimzi operator - https://github.com/strimzi/strimzi-kafka-operator 
         1. Do we need to enable auto-upgrade? YES
      2. Crunchy operator - https://github.com/CrunchyData/postgres-operator 
   3. Do we need to support declarative approaches (gitops/argocd/policies) to install community kafka and postgres?
      1. Strimzi operator - https://github.com/strimzi/strimzi-kafka-operator 
      2. Crunchy operator - https://github.com/CrunchyData/postgres-operator 
   4. Do we need to support installing kafka and postgres via the global hub operator?
      1. Install https://github.com/integr8ly/cloud-resource-operator to provide postgres
      2. Install AMQ stream (different entitlement) https://access.redhat.com/products/red-hat-amq-streams/ 

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