-
Feature Request
-
Resolution: Done
-
Blocker
-
2.2.0.GA
-
None
In CRW 2.2, migration to the new operator metadata bundle format (introduced in OCP 4.4 as a tech preview option) was reverted.
So, we're back to the old format until we start on 2.3. Edit: slip to 2.4 as not all the required pieces for testing are ready to go.
The new bundle format becomes the only supported format in OCP 4.6, but in 4.5 both formats are still supported.
Migration instructions:
- https://docs.engineering.redhat.com/display/CFC/Migration (RH internal wiki / WIP and subject to change)
This is a critical fix for 2.3 so we have time to verify the backport pipeline works before 4.6 goes live.
- blocks
-
CRW-1156 Verify an installation CRW using 'crwctl' on OCP 4.6
- Closed
- is blocked by
-
CRW-1131 Operator needs to be arch-aware and be able to deploy jdk or j9 images as required
- Resolved
- is related to
-
CRW-1287 Adapt CRW testing pipelines to test new CRW 2.5.0 operator bundle
- Closed
-
CRW-1284 Verify CRW 2.4 is installable on OCP 4.6 nightly using bundle index
- Closed
-
CRW-1299 Fix CRW update testing pipelines to test an update from CRW 2.4 to CRW 2.5 with new operator bundle format
- Closed
- relates to
-
CRW-1101 "/v3/plugins/eclipse/che-machine-exec-plugin/7.16.1/meta.yaml was not found on this server" error when start workspace on CRW installed from OperatorHub
- Closed
-
CRW-1202 There are tags instead of digests in codeready-workspaces.csv.yaml generated for rh-osbs-operators registry
- Closed
-
CRW-1157 Verify that registries are able to use RELATED_IMAGE_* values in operator-metatada image
- Closed
-
CRW-1232 Rebuild CRW 2.3 and 2.4 in new bundle format and release to OCP 4.5/4.6 indexes
- Closed
- links to