-
Epic
-
Resolution: Unresolved
-
Major
-
openshift-4.14
-
[upstream] Deppy/Operator API Integration
-
Strategic Product Work
-
17
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-443 - [Phase 1 MVP/Tech Preview] OLM 1.0 - Extension Installation (F7)
-
OCPSTRAT-443[Phase 1 MVP/Tech Preview] OLM 1.0 - Extension Installation (F7)
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
- Integrate the Operator API with Deppy Library
- Ensure integration works well in the initial OLM v1 Milestone 1 goal of enabling basic install/uninstall of operators
Why is this important?
- The Operator API will delegate to Deppy for package selection.
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- The Operator Controller is able to transform existing Operator CRs into PackageNameconstraints
- The Operator Controller specifies GVK Uniqueness Constraints
- The Operator Controller can feed Constraints and Deppy Sources into the Deppy Solver
- The Deppy Solver returns a solution or an error explaining why the set of constraints cannot be satisfied.
Dependencies (internal and external)
- N/A
Previous Work (Optional):
- N/A
Upstream Link:
Open questions:
- N/A
Done Checklist
- CI - CI is running, tests are automated and merged.
- 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>
- is depended on by
-
OCPSTRAT-199 [Phase 1 MVP/Tech Preview] OLM 1.0 - Cluster-level Operator API (B1)
- Closed
-
OCPSTRAT-411 [Phase 1 MVP/Tech Preview] OLM 1.0 - Extension Removal (F16)
- Closed
-
OCPSTRAT-443 [Phase 1 MVP/Tech Preview] OLM 1.0 - Extension Installation (F7)
- Closed