Epic Goal

As a GA feature, the HA support is required. Currently, we support a single instance of postgres which cannot support HA. for postgres HA support, we would consider to setup postgres cluster.

Why is this important?

refer this document about the challenges for postgres - https://docs.google.com/document/d/1Wj5et_PVP4is7XjxKiacER_Hzy9Ad-hUiSw6Yx-Y2VA/edit#heading=h.yzew41ejmt8 

refer to the previous proposal, in order to support centralized postgres and address ACM/MCE requirements, use crunchy operator should be a right direction.

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.