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

Create a new preview OLM channel for AllNamespace mode + DWO dependency (OCP 4.8+)

    XMLWordPrintable

Details

    • False
    • False
    • Undefined

    Description

      In upstream it is created a new channel to install Eclipse Che Operator in AllNamespace mode and add the DevWorkspace OLM dependency.
      (As of Sept 7, this channel is called "tech-preview-stable-all-namespaces".)

      Related issue: https://github.com/eclipse/che/issues/19891
      Related upstream PR: https://github.com/eclipse-che/che-operator/pull/890

      In CodeReady Workspace would be nice to have a similar channel to start to see how the installation in AllNamespaces mode is working for CodeReady workspaces with DWO olm dependency

      Suggested new channel names:

      • stable-ocp46-eus [2.11, 2.12, ... - see CRW-2128]
      • fast-ocp46-eus [currently empty, nothing to put here as no new tech preview stuff being rolled out for 4.6]
        and
      • stable-ocp48 [2.11, 2.12, ... - see CRW-2128]
      • fast-ocp48 [2.11 w/ allnamespaces + DWO enabled, 2.12, ...]
      • candidate-ocp48 [2.x CI builds only, likely out of scope for 2.11 - see CRW-1759]
        and
      • latest - if we keep this, I would point it at ocp46-eus-stable; but I would argue 2.11 is a good time to REMOVE the "latest" channel
         
        In future we would add ocp49 and ocp410-eus suffixed channels, but until content deprecation (OCP 4.10) or cross-channel updates (OCP 4.?) are feasible, users will have to manage their own manual subscription paths.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. CRW-2303 Unable to start che-gateway from `tech-preview`OLM channels

          • 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-2241 OLM channels changes when DW milestone 3 completes: remove latest and make stable the default

          • 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
          causes

          Bug - A problem that impairs or prevents the functions of the product. CRW-2296 Operator container failed to initialize default value: 'RELATED_IMAGE_devworkspace_controller'

          • 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 related to

          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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. CRW-2320 Installation of CRW with crwctl cli from the tech-preview channel failed

          • 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-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 Upstream issue

          mentioned on

          GitLab Merge request - CRW-2095-bundle-build-part2

          GitLab Merge request - Draft: CRW-2095 add build for crw-operator-bundle

          Activity

            People

              flacatus Flavius Lacatusu
              flacatus Flavius Lacatusu
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: