Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-1044

Switch operator metadata to new bundle format (OCP 4.5+) and ensure that backporting to OCP 4.3+ works

    XMLWordPrintable

Details

    Description

      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:

      This is a critical fix for 2.3 so we have time to verify the backport pipeline works before 4.6 goes live.

      Attachments

        Issue Links

          blocks

          QE Task - QE Task CRW-1156 Verify an installation CRW using 'crwctl' on OCP 4.6

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is blocked by

          Feature Request - Feature requests from customers and/or users CRW-1131 Operator needs to be arch-aware and be able to deploy jdk or j9 images as required

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          is related to

          QE Task - QE Task CRW-1287 Adapt CRW testing pipelines to test new CRW 2.5.0 operator bundle

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          QE Task - QE Task CRW-1284 Verify CRW 2.4 is installable on OCP 4.6 nightly using bundle index

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          QE Task - QE Task CRW-1299 Fix CRW update testing pipelines to test an update from CRW 2.4 to CRW 2.5 with new operator bundle format

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. 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

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CRW-1202 There are tags instead of digests in codeready-workspaces.csv.yaml generated for rh-osbs-operators registry

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. CRW-1157 Verify that registries are able to use RELATED_IMAGE_* values in operator-metatada image

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. CRW-1232 Rebuild CRW 2.3 and 2.4 in new bundle format and release to OCP 4.5/4.6 indexes

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          links to

          Web Link CFC Migration Guide for Operators

          Activity

            People

              nickboldt Nick Boldt
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: