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

Improve MachineConfigPool page to support ability to update control plane only


    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • HAC Infra - Sprint 219

      Improve the UX on the machine config pool page to reflect the new enhancements on the cluster settings that allows users to select the ability to update the control plane only.

      Currently in the console, users only have the ability to complete a full cluster upgrade. For many customers, upgrades take longer than what their maintenance window allows. Users need the ability to upgrade the control plane independently of the other worker nodes. 

      Ex. Upgrades of huge clusters may take too long so admins may do the control plane this weekend, worker-pool-A next weekend, worker-pool-B the weekend after, etc.  It is all at a pool level, they will not be able to choose specific hosts.


      1. Changes to the table:
        1. Remove "Updated, updating and paused" columns. We could also consider adding column management to this table and hide those columns by default.
        2. Add "Update status" as a column, and surface the same status on cluster settings. Not true or false values but instead updating, paused, and up to date.
        3. Surface the update action in the table row.
      2. Add an inline alert that lets users know there is a 60 day window to update all worker pools. In the alert, include the sentiment that worker pools can remain paused as long as is normally safe, which means until certificate rotation becomes critical which is at about 60 days. The admin would be advised to unpause them in order to complete the full upgrade. If the MCPs are paused, the certification rotation does not happen, which causes the cluster to become degraded and causes failure in multiple 'oc' commands, including but not limited to 'oc debug', 'oc logs', 'oc exec' and 'oc attach'. (Are we missing anything else here?) Add the same alert logic to this page as the cluster settings:
        1. From day 60 to day 10 use the default inline alert.
        2. From day 10 to day 3 use the warning inline alert.
        3. From day 3 to 0 use the critical alert and continue to persist until resolved.

      Design deliverables: 

        1. Screen Shot 2022-05-10 at 10.09.35 AM.png
          Screen Shot 2022-05-10 at 10.09.35 AM.png
          205 kB
        2. 13.2 copy 30.png
          13.2 copy 30.png
          180 kB
        3. 13.2 copy 27.png
          13.2 copy 27.png
          180 kB
        4. 13.2 copy 24.png
          13.2 copy 24.png
          179 kB
        5. 13.2 copy 21.png
          13.2 copy 21.png
          133 kB

            rhn-engineering-rhamilto Robb Hamilton
            mehall-1 Megan Hall
            Xiyun Zhao Xiyun Zhao
            0 Vote for this issue
            4 Start watching this issue