Loading...

XML

Word

Printable

Epic Name:
Openshift Console / Editing Cluster Autoscaler default value - Support for 249 nodes
Blocked:
False
Blocked Reason:

Hide

Max Node limits are going to be returned from backend API, being tracked via https://issues.redhat.com/browse/OCM-11039

Show
Max Node limits are going to be returned from backend API, being tracked via https://issues.redhat.com/browse/OCM-11039
Ready:
False
Epic Status:
To Do
Feature Link:
XCMSTRAT-161 - OSD & ROSA Classic scale to and upgrade with 249 nodes
Hierarchy Progress Bar:

50% To Do, 50% In Progress, 0% Done

Overview

When users open the UI console's modal to adjust the cluster's autoscaler max node total, it currently portrays a "default" value of 180.

This is incorrect under certain scenarios. We are going to do a short and long term solution.

Short term.
1. Change 180 to 249 in both day 1 & 2 'Cluster Autoscaler Settings'. (A CONST in the UI)
2. Add validation if user enters something over 249 (we currently don't do this!)
3. Add tooltip to explain to user how to properly calc. and set the 'max nodes total'.
4. 249 is the absolve max, however it will be lower in certain cluster configs depending on single zone and multi zone, and number of already existing nodes.
  Backend will do final validation of the value during cluster creation and it does return a pretty clear error message.
Long Term
1. It has be determined in this slack thread that rather than the UI using a CONST or doing calculations; it would be better if the backend API returns a set of values, so that CLI and UI have 'single source of truth'.
  The backend might send a list or map of all possible default values to the front end one time, and the frontend decides which value to return back to the user based on selections (single .vs MZ) made on the front end. This part is going to be tracked in a different Epic