-
Epic
-
Resolution: Done
-
Undefined
-
None
-
Rename Operator and Catalog to ClusterExtension and ClusterCatalog
-
Upstream
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-1375 - [Tech Preview phase III] Next-gen OLM (OLM v1)
-
-
0% To Do, 0% In Progress, 100% Done
-
XS
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
- OLM v1 currently has a CRD named Operator. The goal of this epic is to rename those APIs from Operator to ClusterExtension.
Why is this important?
- There are two main reasons for renaming Operator to ClusterExtension:
- Operator is a name that is already owned by an OLM v0 CRD that has a totally different meaning, spec and status, and OLM v0 and v1 need to be able to live on the same cluster at the same time.
- OLM is moving to a model where it manages more than just Operators. Cluster Extensions are a better abstraction for the different types of packages that OLM will be able to install in future releases.
Scenarios
- ...
Acceptance Criteria
- OLM v1's installation should include a new API called ClusterExtension
Dependencies (internal and external)
- ...
Previous Work (Optional):
- Upstream ClusterExtension change: https://github.com/operator-framework/operator-controller/pull/568
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>
