Uploaded image for project: 'OpenShift UX Product Design'
  1. OpenShift UX Product Design
  2. PD-1226

[OCP] Support conditional updates (a.k.a. targeted edge blocking) for 4.11

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Major
    • Admin
    • None
    • False
    • False
    • Admin UXD Sprint 214, Admin UXD Sprint 215, Admin UXD Sprint 216, Admin UXD Sprint 217, Admin UXD Sprint 218, Admin UXD Sprint 220

    Description

      Goal
      Add the ability for users to select supported but not recommended updates.

      Background
      RFE: for 4.10, Cincinnati and the cluster-version operator are adding conditional updates (a.k.a. targeted edge blocking): https://issues.redhat.com/browse/OTA-267

      High-level plans in https://github.com/openshift/enhancements/blob/master/enhancements/update/targeted-update-edge-blocking.md#update-client-support-for-the-enhanced-schema

      Example of what the oc adm upgrade UX will be in https://github.com/openshift/enhancements/blob/master/enhancements/update/targeted-update-edge-blocking.md#cluster-administrator.

      The oc implementation landed via https://github.com/openshift/oc/pull/961.

      Requirements

      • Identify the optimal UX so that users can select supported but not recommended updates when applicable. Consider things like, do we want users to opt into seeing these versions or do we always want to make them visible but make it explicitly clear that they are not recommended?
      • Identify the optimal UX so that users understand the reason those edges are not recommended for their particular cluster.

      Design
      Google Doc
      Sketch
      Marvel

      Attachments

        Issue Links

          blocks

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. CONSOLE-3094 Support Conditional Updates (a.k.a. Targeted Edge Blocking)

          • 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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CONSOLE-3138 Support Conditional Updates - Cluster update "Update Version" modal

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CONSOLE-3136 Support Conditional Updates - Cluster settings page

          • Undefined - Priority not specified.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CONSOLE-3137 Support Conditional Updates - Cluster update "Other available paths" modal

          • Undefined - Priority not specified.
          • Closed
          is blocked by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OTA-267 Add capability for targeted edge blocking

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

          Activity

            People

              tle@redhat.com Thi Le (Inactive)
              mehall-1 Megan Hall
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: