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

• The Cluster CAPI Operator enhancement (https://github.com/openshift/enhancements/pull/1845) introduces a CRD
    Compatibility Checker to prevent incompatible CRD updates. ACM needs to integrate with this mechanism when
    deploying and managing Cluster API resources.
• Work Items:
    1. Review the CRD Compatibility Checker enhancement proposal
    2. Verify CRD installation process when ACM deploys HyperShift or Cluster API components
    3. Ensure proper namespace and object selectors are configured for ValidatingWebhook
    4. Implement compatibility checks during ACM-driven cluster deployments
    5. Collaborate with CCAPIO and HCP teams on CRD management coordination
    6. Update ACM documentation for CRD compatibility requirements
    7. Test multi-actor CRD scenarios (ACM + CCAPIO + HCP)

Why is this important?

• It is very unlikely we will be able to co-exist, and therefore need a way to handle the upgrade case safely to ensure neither side gets broken during the upgrade

Scenarios

1. ...

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. …

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>