-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
CRD Compatibility Checker Phase 1
-
Product / Portfolio Work
-
-
61% To Do, 17% In Progress, 22% Done
-
False
-
-
False
-
Not Selected
-
L
-
None
Epic Goal
Develop and integrate the CRD checking functionality of CRD Compatibility Checker, without unknown fields checking
Why is this important?
This is the most critical functionality of CRD Compatibility Checker. It is sufficient to implement the majority of the CRD Upgrade Safety feature in cluster-capi-operator, and for other stakeholders to integrate with.
Scenarios
From CRD Compatibility Checker all use cases except UC4.
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Open questions::
- …
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>
