-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
4.10
-
None
-
CLOUD Sprint 233
-
1
-
False
-
Description of problem:
ClusterAutoscaler does not scale the nodes evenly in AzurePublicCloud OCP IPI
Version-Release number of selected component (if applicable):
4.10.30
How reproducible:
100%
Steps to Reproduce:
1. Install an OCP cluster on AzurePublicCloud. 2. Create 3 machinesets each in single AZ 3. Use the below ClusterAutoscaler definition: apiVersion: autoscaling.openshift.io/v1 kind: ClusterAutoscaler metadata: name: default spec: podPriorityThreshold: -10 ignoreDaemonsetsUtilization: true balanceSimilarNodeGroups: true scaleDown: enabled: true delayAfterAdd: 30m delayAfterDelete: 5m delayAfterFailure: 3m unneededTime: 60m 4. Deploy application workload to trigger node scaleup
Actual results:
Uneven node scale up happens, for example like below: # oc get machinesets -A NAMESPACE NAME DESIRED CURRENT READY AVAILABLE AGE openshift-machine-api useast2-2-frqmg-worker-eastus21 7 7 7 7 4d6h openshift-machine-api useast2-2-frqmg-worker-eastus22 3 3 3 3 4d6h openshift-machine-api useast2-2-frqmg-worker-eastus23 19 19 19 19 4d6h ```
Expected results:
The nodes should be evenly spread across all the availability zones.
Additional info: