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

Do not automatically update CRW to a new version if the cluster runs an unsupported OCP version

    XMLWordPrintable

Details

    • False
    • False
    • Undefined

    Description

      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:

      References:

      Attachments

        Issue Links

          is related to

          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

          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

          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

          Task - Represents a small unit of work that is not end-user facing. CRW-2138 operator-metadata bundle cannot declare incompatibility with v4.7 (commas not allowed)

          • 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
          mentioned on

          GitLab Merge request - chore: CRW-2128 CRW-2674 CRW 2.13+ is not supported on OCP 4.6-4.7 (and should...

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: