-
Story
-
Resolution: Done
-
Major
-
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
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
- blocks
-
CONSOLE-3094 Support Conditional Updates (a.k.a. Targeted Edge Blocking)
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is blocked by
-
-
- Closed
-