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

OLM channels changes when DW milestone 3 completes: remove latest and make stable the default

    XMLWordPrintable

Details

    • 8
    • False
    • False

    Description

      When the 3rd milestone of the DevWorkspace integration gets completed we should enable DWO by default on CRW. That means that:

      • the all-namespaces channel must be renamed stable and become the default channel
      • we should stop releasing latest channel
      • the bundle.package name should revert to codeready-workspaces, not codeready-workspaces2 so that users in the latest channel can switch to stable without having to uninstall bundle codeready-workspaces to install codeready-workspaces2.
      • temporarily, the stable channel bundle csv will have NO replaces: directive until 2.16.0 is live. Ref: CRW-2196

      Existing customers that will want to upgrade from channel latest to stable will have to follow the instructions described here:

      • Remove all subscriptions created for CRW installed from latest channel.
      • IMPORTANT: removing subscriptions does not mean CRW operands such as che-server, keycloak or roles will be removed from the cluster. These will be updated once the new subscription is enabled.
      • If running OCP earlier than 4.8, update from OCP 4.6 EUS to 4.7, and from OCP 4.7 to 4.8.
      • Enable subscription for stable channel, which is supported only for OCP 4.9+ (as OCP 4.10 EUSwill be available to replace 4.8 EUS).

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. CRW-2137 CRW Operator should not manage DWO resources

          • 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. CRW-2196 2.x operator bundle builds can't use replaces: for an unreleased operator version (2.12 -> 2.11)

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

          Task - Represents a small unit of work that is not end-user facing. CRW-2095 Create a new preview OLM channel for AllNamespace mode + DWO dependency (OCP 4.8+)

          • 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
          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. CRW-2571 There are 2 instances of CRW on OperatorHub and admins get confused

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

          Feature Request - Feature requests from customers and/or users CRW-2797 Add CRW 2.15.2 to OCP 4.10 index

          • 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.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. CRW-2725 Re-enable replaces directive in operator-bundle sync*.sh and csv files

          • 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.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. CRW-2799 devspaces operator fails package uniqueness test

          • 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-2804 Request removal of both tech preview operator-bundle `codeready-workspaces2` and GA operator-metadata `codeready-workspaces` from OCP 4.11 indexes

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

          Task - Represents a small unit of work that is not end-user facing. RHDEVDOCS-3810 Support considerations for Dev Spaces 3.0

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

          Task - Represents a small unit of work that is not end-user facing. CRW-2128 Do not automatically update CRW to a new version if the cluster runs an unsupported OCP version

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

          Web Link DevWorkspace Integration - STEP3

          mentioned on

          GitLab Merge request - chore: CRW-2241 remove bundle and metadata images from the OCP 4.10 index

          Activity

            People

              nickboldt Nick Boldt
              mloriedo Mario Loriedo
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: