Details
-
Epic
-
Resolution: Done
-
Major
-
None
-
Add External platform type and ensure operators do not react
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-516 - [Phase 1] Add a new platform type ("external") to identify clusters with non-integrated partner components enabled
-
OCPSTRAT-516[Phase 1] Add a new platform type ("external") to identify clusters with non-integrated partner components enabled
-
100
-
100%
Description
Epic Goal
- As defined in the part (
OCPBU-5), this epic is about adding the new "External" platform type and ensuring that the OpenShift operators which react to platform types treat the "External" platform as if it were a "None" platform. - Add an end-to-end test to exercise the "External" platform type
Why is this important?
- This work lays the foundation for partners and users to customize OpenShift installations that might replace infrastructure level components.
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
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>
Attachments
1.
|
QE Tracker |
|
Closed | 
|
Unassigned |
