-
Initiative
-
Resolution: Done
-
Major
-
None
-
None
-
Future Sustainability
-
None
-
0% To Do, 0% In Progress, 100% Done
-
False
-
-
False
-
None
-
None
-
None
OLMv1 features that are not ready for GA may directly impact the contents of the CRDs provided by operator-controller and catalogd. This includes the addition of new fields and values in the CRD API that may not have any functionality, or even different functionality, unless a given feature gate is enabled.
This means that users may attempt to use these APIs even though they don’t do anything and this can cause confusion. These APIs may not be fully documented, or may even be in flux.
This is especially important when code is released officially, either as part of the operator-framework open source project or as part of OpenShift. In both cases, only GA’d features and API should be available by default. No non-GA’d features should be accessible and neither should corresponding APIs.
All non-GA’d features must be explicitly enabled as experimental or tech preview. In which case, the APIs for those features must become available as part of the CRD.
Brief: https://docs.google.com/document/d/1L6e_0eSO6FeXoW4LBs6cNKCWPS9gAROcW5tSu7Rv8wM/edit?tab=t.0
- relates to
-
OCPSTRAT-1873 OLMv1: Downstream Feature Gate Promotion Mechanics
-
- Closed
-
- links to
