OCP/Telco Definition of Done
Epic Template descriptions and documentation.

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

Epic Goal

• Follow-up to the initial phase 0 (OLM-2513) Epic for any nice-to-have feature work or any process work that still needs to be done for platform operators. The OLM-2513 Epic introduces the high-level platform operators manager (POM) component, and an aggregate ClusterOperator controller which is responsible for acting as a proxy for the underlying PlatformOperator resources in the cluster and the core CVO component.

Why is this important?

• Extends the core phase 0 functionality, and introduces a couple of small, net-new features. One of those small features includes implementing a "core" ClusterOperator controller for the POM component. This helps deliver a more robust component implementation for this initial platform operators phase. Another key feature is trying to ensure that the PlatformOperator resources in the cluster specify a unique package name to provide a better admin UX when misconfiguring platform operators in the cluster.

Scenarios

1. N/A.

Acceptance Criteria

• All stories marked as completed or moved into a new epic (or the backlog).

Dependencies (internal and external)

1. OLM-2513

Previous Work (Optional):

1. OLM-2513

Open questions::

1. N/A.

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>