Description of problem:

    When enable the scaling from zero feature in AWS and if a NodePool has InPlace node update type and set the autoscaling min=0, the new workload won't scale up the nodepool.

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

How reproducible:

Steps to Reproduce:

• Install hypershift operator with scaling from zero feature enabled and created a cluster

  hypershift install 
  --scale-from-zero-aws-creds "config/awscredentials"
  

• Create a InPlace nodepool

  hypershift create nodepool aws --name np-scale-zero --cluster-name zero --namespace clusters --node-upgrade-type InPlace --replicas 0
  

• Enable NodePool's autoscaling and set min=0

  oc patch nodepool np-scale-zero -n clusters --type=json -p='[
      {"op": "remove", "path": "/spec/replicas"},
      {"op": "add", "path": "/spec/autoScaling", "value": {"min": '0', "max": '3'}}
  ]'
  

• Create workload to the hosted cluster

Actual results:

No new nodes created/scale up because of workload
    

Expected results:

The nodepool: np-scale-zero  should scale up to 3 which means 3 more nodes running.
    

Additional info: