-
Epic
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
Enable OLM v1 to be on by default
-
Strategic Product Work
-
13
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-1347 - [GA release] Next-gen OLM (OLM v1)
-
-
0% To Do, 18% In Progress, 82% Done
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
- Once OLM v1.0.0 is feature complete and the team feels comfortable enabling it by default, we should remove the OLM v1 feature flag and deploy it on all clusters by default.
- We should also introduce OLMv1 behind a CVO capability to give customers the option of leaving it disabled in their clusters.
Why is this important?
- …
Scenarios
- ...
Acceptance Criteria
- OLMv1 is enabled by default in OCP
- OLMv1 can be fully disabled at install/upgrade time using CVO capabilities
- 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>
- causes
-
OCPBUGS-44767 TP cluster upgrade stuck on customresourcedefinition olms.operator.openshift.io
-
- New
-
-
-
- Closed
-
- is cloned by
-
-
- Release Pending
-
- links to
