Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-2729

Console UI calculations for cluster autoscaler max node total - day2

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • Core UI
    • 3
    • OCMUI Core Sprint 263

      Related to: https://redhat-internal.slack.com/archives/C07NMT1504E/p1732215570120939

       

      When users enable the cluster autoscaler, 

      the current default value and greyed out text field value is set as 180.

      In order to portray a more accurate value for the users when enabling the cluster autoscaler via the toggle, both the default value and prefilled text value for the cluster autoscaler needs to consider the following calculation:

       
       Display max-nodes-total pre-filed value and the 'Default value' under this field based on the cluster version * Since XCMSTRAT-161 (support for 249 compute nodes) validation was based on v4.14.14,  the values will be set to:

        • 249+master+infra for ROSA classic and OSD clusters >= 4.14.14
        • 180 (current scaling limit)+master+infra for ROSA classic and OSD clusters < 4.14.14

       

                    ***This calculation should be applied on day 1 as well - ROSA classic wizard and OSD wizard *** 

       

      The user will have an option to edit the input field, and UI will have inline validation that compares the user input against the 'Default value' printed below the input field.
       
      The number of master nodes is fixed at 3
      The number of infra nodes are based on single az (2) vs. multi az (3)
       
       
      Please note, once the user enables the cluster autoscaler and sets the maxnodetotal value, it needs to retrieve what was last saved.
       

              rh-ee-egilman Liza Gilman (Inactive)
              dle.openshift David Lee
              Jason Loss Jason Loss
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: