-
Task
-
Resolution: Done
-
Critical
-
2.13.1.GA, 2.14.0.GA, 2.15.0.GA
-
None
-
False
-
False
-
Undefined
-
Every new version of CRW is pushed to channel latest (upstream Che uses stable. No matter what's the OCP version of the cluster, if automatic updates are enabled, CRW will be updated to the latest stable version. That means that CRW will be automatically updated to v2.11 on an OCP 4.7 cluster although v2.11 doesn't support that version of OCP
Two alternative proposals to fix this behavior are:
- using a dedicated channel per OCP version
- specify olm.maxOpenShiftVersion in the CSV
References:
- Channel Version Guide
- CFC Delivery
- OLM Channel Naming (candidate/fast/stable)
- Index Config new in OCP 4.8+
- is related to
-
CRW-2095 Create a new preview OLM channel for AllNamespace mode + DWO dependency (OCP 4.8+)
- Closed
-
CRW-2241 OLM channels changes when DW milestone 3 completes: remove latest and make stable the default
- Closed
-
RHDEVDOCS-3810 Support considerations for Dev Spaces 3.0
- Closed
-
CRW-2138 operator-metadata bundle cannot declare incompatibility with v4.7 (commas not allowed)
- Closed
- mentioned on