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

Adopt new cert signing APIs in the proxy-addon from MCE 2.6 to properly connect to the hub proxy.

Why is this important?

To be able to keep things working when a cluster backup/restore is done and connection between the metrics-collector in spokes and observatorium api in the hub stays working with the updated certs.

Details: https://redhat-internal.slack.com/archives/CUU609ZQC/p1709114646026109?thread_ts=1709088237.144099&cid=CUU609ZQC

Scenarios

ACM Hub with spokes using the hub-proxy.

Acceptance Criteria

• Get a cluster running that uses the hub-proxy.
• Backup the cluster.
• Restore it.
• MCO should still work.

Dependencies (internal and external)

1. MCE with hub-proxy.

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.