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

• ClusterExtensions apply a set of resources to the cluster. This epic ensures that, if one of those resources was created and is currently owned by another ClusterExtension resource, the ClusterExtension should fail to apply.

Why is this important?

• More than one Operator managing the same resource will lead to instability and a bad user experience

Scenarios

1. Two users try to install the same package
2. A user tries to install a package but one or more resources of the chosen bundle already exist on cluster

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. Upstream parent issue: https://github.com/operator-framework/operator-controller/issues/736 

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>