Epic Goal

• Understand how Postgresql is provided by the following teams:

• • Search
  • Global hub
  • Assisted Installer
  • Policy Compliance History
  • Maestro (coming)
• Search is a mature offering in the product, Global Hub has seen a lot of work to ready its postgresql offering.  Assisted is also a mature use case.
• SPIKE
  • Tactical, choose one of the mature offerings to standardize on
  • Delivery method
    • Crunchy
    • Existing instance from one of the components
  • Define ownership agreement
    • Who
    • How
    • With what

Why is this important?

We don't want to manage 5x distinct instances. There is already ART in the product since its inception that ran postgresql, the team should be leveraging this.

Scenarios

• Centralized Postgresql for use with Search, Assisted Installer and Policy Compliance history
• Reuse the postgresql management flow for Global Hub (does GH always have an ACM on the cluster?)

Acceptance Criteria

• Central instance of postgresql
• Ownership

Dependencies (internal and external)

1. Search
2. Assisted Installer
3. Policy Compliance History
4. Maestro
5. Global Hub
6. Common Inventory (maybe)
7. Backup and Restore (DR squad)

Previous Work (Optional):

1. Search, Assisted and Global Hub all have well defined postgresql instances
2. Backup and restore process for these instances (Assisted has one)

Open questions:

1. Which instance do we choose?
2. Is there an operator like Crunchydb that we should rally around
3. Who will own
4. Can we generalize the interface, will there be a new CR to get access to the postgresql instance

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.