Uploaded image for project: 'OpenShift Console'
  1. OpenShift Console
  2. CONSOLE-2927

Add Control Plane Upgrade to Web Console

    XMLWordPrintable

Details

    • Add Control Plane Upgrade to Web Console
    • False
    • False
    • console
    • To Do
    • OCPSTRAT-180 - Improve upgrades - phase 1
    • OCPSTRAT-180Improve upgrades - phase 1
    • 100
    • 100% 100%
    • Undefined

    Description

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • Provide a one click option to perform an upgrade which pauses all non master pools

      Why is this important?

      • Customers are increasingly asking that the overall upgrade is broken up into more digestible pieces
      • This is the limit of what's possible today
        • R&D work will be done in the future to allow for further bucketing of upgrades into Control Plane, Worker Nodes, and Workload Enabling components (ie: router) That will however take much more consideration and rearchitecting

      Scenarios

      1. An admin selecting their upgrade is offered two options "Upgrade Cluster" and "Upgrade Control Plane"
        1. If the admin selects Upgrade Cluster they get the pre 4.10 behavior
        2. If the admin selects Upgrade Control Plane all non master pools are paused and an upgrade is initiated
      2. A tooltip should clarify what the difference between the two are
      3. The pool progress bars should indicate pause/unpaused status, non master pools should allow for unpausing

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. While this epic doesn't specifically target upgrading from 4.N to 4.N+1 to 4.N+2 with non master pools paused it would fundamentally enable that and it would simplify the UX described in Paused Worker Pool Upgrades

      Open questions::

      1. …

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

      Attachments

        Issue Links

          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CONSOLE-2976 Add the ability to update control plane only to Cluster Settings

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

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MCO-77 Improve kubelet CA update for Paused Machine Config Pools

          • 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

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OTA-454 R&D Breaking up Upgade into Control Plane, Worker Nodes, Workload Enablement

          • 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

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPPLAN-5484 OpenShift 4 EUS to EUS upgrades

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

          GitHub openshift/console#11053: CONSOLE-2976: add update mode to Update cluster

          There are no Sub-Tasks for this issue.

          Activity

            People

              amobrem Ali Mobrem
              rhn-support-sdodson Scott Dodson
              Xiyun Zhao Xiyun Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: