Description of problem:

For any hive provisioned cluster, we can edit the number minimum number of machine set replica counts from 0+ by selecting scale machine pool, however when enabling autoscale, the only option is to scale from 3 or higher (in this case, provisioned cluster has 3 master/3 worker)

In addition, for SNO clusters, this minimum is 6 (although current number of replica sets is at 0, and when manually scaling we can select 0+):

Version-Release number of selected component (if applicable):

ACM 2.9.0-DOWNSTREAM-2023-10-02-21-22-22

How reproducible:

always

Steps to Reproduce:

1. provision a default (3 master, 3 worker) cloud cluster (e.g. azure) via ACM and/or a SNO cluster via ACM
2. go to cluster overview page > machine pools
3. for the machine pool, select options and click "enable autoscale"

Actual results:

Expected results:

Additional info:

ACM 2.9.0 Deferral request

Deferral Request:

• Brief summary on why you would like to defer this:
  • We want to defer this issue to provide more time for dev to investigate and determine a suitable response/fix.
• What is the impact to the customer if the bug is not fixed?
  • The impact is negligible as there is no customer RFE and there are several work arounds to scaling the minimum replicas down.
• Will the customer see this as a regression?
  • No
• High-level summary of what the fix would be:
  • We need to align the console's behavior with respect to autoscaler modals, across provisioned and SNO clusters, as well as ensure the modals enforce their minimum values thoroughly, as of now the user can still drop a minimum replica value by just editing the value in the modal. 
• What is a workaround, if any?
  • Manually alter the machinepool spec.autoscaler
  • Edit the value of the modal minimum replica instead of using the minus button.

• Should this issue be added to the Release Notes (Please create a Doc Task if needed)?
  • No