Sync upstream v1.31.1

[aaronfern]

What this PR does / why we need it:
Sync with upstream autoscaler v1.31.1

Which issue(s) this PR fixes:
Fixes #320

Special notes for your reviewer:

Release note:

Synced changes till v1.31.1 of upstream autoscaler

[elankath]

/lgtm

[aaronfern]

Integration test run

=========================================================================================================
Random Seed: 1741241542

Will run 12 of 12 specs
------------------------------
[BeforeSuite]
/Users/i544000/go/src/k8s.io/autoscaler/cluster-autoscaler/integration/integration_test.go:30
Scaling Cluster Autoscaler to 0 replicas
  STEP: Adjusting node groups to initial required size @ 03/06/25 11:42:29.728
  STEP: Marking nodes present before the tests as unschedulable @ 03/06/25 11:42:30.129
  STEP: Taint node ip-10-180-24-84.eu-west-1.compute.internal @ 03/06/25 11:42:30.327
  STEP: Starting Cluster Autoscaler.... @ 03/06/25 11:42:31.085
[BeforeSuite] PASSED [4.827 seconds]
------------------------------
Cluster Autoscaler test Scale up and down nodes by deploying new workload requesting more resources should not lead to any errors and add 1 more node in target cluster
/Users/i544000/go/src/k8s.io/autoscaler/cluster-autoscaler/integration/integration_test.go:100
  STEP: Checking autoscaler process is running @ 03/06/25 11:42:31.097
  STEP: Deploying workload... @ 03/06/25 11:42:31.097
  STEP: Validating Scale up @ 03/06/25 11:42:31.3
• [118.031 seconds]
------------------------------
Cluster Autoscaler test Scale up and down nodes by scaling deployed workload to 3 replicas should not lead to any errors and add 3 more node in target cluster
/Users/i544000/go/src/k8s.io/autoscaler/cluster-autoscaler/integration/integration_test.go:115
  STEP: Checking autoscaler process is running @ 03/06/25 11:44:29.126
  STEP: Scaling up workload to 3 replicas... @ 03/06/25 11:44:29.126
  STEP: Validating Scale up @ 03/06/25 11:44:29.525
• [96.303 seconds]
------------------------------
Cluster Autoscaler test Scale up and down nodes by scaling down the deployed workload to 0 should not lead to any errors and 3 nodes to be removed from the target cluster
/Users/i544000/go/src/k8s.io/autoscaler/cluster-autoscaler/integration/integration_test.go:130
  STEP: Checking autoscaler process is running @ 03/06/25 11:46:05.525
  STEP: Scaling down workload to zero... @ 03/06/25 11:46:05.525
  STEP: Validating Scale down @ 03/06/25 11:46:05.921
  STEP: Deleting workload @ 03/06/25 11:47:16.083
  STEP: Checking that number of Ready nodes is equal to initial @ 03/06/25 11:47:16.283
• [70.959 seconds]
------------------------------
Cluster Autoscaler test testing annotation to skip scaledown by adding annotation and then scaling the workload to zero should not scale down the extra node and should log correspondingly
/Users/i544000/go/src/k8s.io/autoscaler/cluster-autoscaler/integration/integration_test.go:147
  STEP: Checking autoscaler process is running @ 03/06/25 11:47:16.484
  STEP: adding the annotation after deploy workload to 1 @ 03/06/25 11:47:16.484
  STEP: Validating Scale up @ 03/06/25 11:47:16.685
  STEP: getting the latest added node and adding annotation to it. @ 03/06/25 11:48:40.957
  STEP: Scaling down workload to zero... @ 03/06/25 11:48:41.366
• [103.366 seconds]
------------------------------
Cluster Autoscaler test testing annotation to skip scaledown by adding annotation and then scaling the workload to zero Should remove the unwanted node once scale down disable annotation is removed
/Users/i544000/go/src/k8s.io/autoscaler/cluster-autoscaler/integration/integration_test.go:172
  STEP: Checking autoscaler process is running @ 03/06/25 11:48:59.849
  STEP: getting the latest added node and removing annotation from it. @ 03/06/25 11:49:00.444
  STEP: Validating Scale down @ 03/06/25 11:49:00.855
  STEP: Deleting workload @ 03/06/25 11:49:52.795
  STEP: Checking that number of Ready nodes is equal to initial @ 03/06/25 11:49:52.995
• [53.353 seconds]
------------------------------
Cluster Autoscaler test testing min and max limit for Cluster autoscaler by increasing the workload to above max shouldn't scale beyond max number of workers
/Users/i544000/go/src/k8s.io/autoscaler/cluster-autoscaler/integration/integration_test.go:193
  STEP: Checking autoscaler process is running @ 03/06/25 11:49:53.202
  STEP: Deploying workload with replicas = max+4 @ 03/06/25 11:49:53.202
  STEP: Validating Scale up @ 03/06/25 11:49:53.403
• [93.873 seconds]
------------------------------
Cluster Autoscaler test testing min and max limit for Cluster autoscaler by decreasing the workload to below min shouldn't scale down beyond min number of workers
/Users/i544000/go/src/k8s.io/autoscaler/cluster-autoscaler/integration/integration_test.go:205
  STEP: Checking autoscaler process is running @ 03/06/25 11:51:27.074
  STEP: Scaling down workload to zero... @ 03/06/25 11:51:27.075
  STEP: Validating Scale down @ 03/06/25 11:51:27.495
  STEP: Deleting workload @ 03/06/25 11:52:35.361
  STEP: Checking that number of Ready nodes is equal to initial @ 03/06/25 11:52:35.565
• [68.695 seconds]
------------------------------
Cluster Autoscaler test testing scaling due to taints make current nodes unschedulable should spawn more nodes for accommodating new workload
/Users/i544000/go/src/k8s.io/autoscaler/cluster-autoscaler/integration/integration_test.go:221
  STEP: Checking autoscaler process is running @ 03/06/25 11:52:35.769
  STEP: making the only node available, to be unschedulable @ 03/06/25 11:52:35.769
  STEP: Taint node ip-10-180-79-175.eu-west-1.compute.internal @ 03/06/25 11:52:35.968
  STEP: Increasing the workload @ 03/06/25 11:52:36.375
  STEP: Validating Scale up @ 03/06/25 11:52:36.577
• [99.505 seconds]
------------------------------
Cluster Autoscaler test testing scaling due to taints make current nodes unschedulable should remove the node as the taint has been removed and node has low utilization
/Users/i544000/go/src/k8s.io/autoscaler/cluster-autoscaler/integration/integration_test.go:238
  STEP: Checking autoscaler process is running @ 03/06/25 11:54:15.274
  STEP: making the node available to be schedulable @ 03/06/25 11:54:15.274
  STEP: Removing taint(s) from node ip-10-180-79-175.eu-west-1.compute.internal @ 03/06/25 11:54:15.476
  STEP: Validating Scale down @ 03/06/25 11:54:15.886
  STEP: Deleting workload @ 03/06/25 11:55:22.872
  STEP: Checking that number of Ready nodes is equal to initial @ 03/06/25 11:55:23.072
• [68.000 seconds]
------------------------------
Cluster Autoscaler test testing scaling due to volume pending create a volume in a zone with no node and a pod requesting it should create a node in the zone with volume and hence scale up
/Users/i544000/go/src/k8s.io/autoscaler/cluster-autoscaler/integration/integration_test.go:257
  STEP: Checking autoscaler process is running @ 03/06/25 11:55:23.274
  STEP: Creating StorageClass with topology restrictions @ 03/06/25 11:55:23.274
  STEP: deploying PVC in zone with no nodes @ 03/06/25 11:55:23.471
  STEP: deploying the workload which requires the volume @ 03/06/25 11:55:23.673
  STEP: Validation scale up to +1 in a new Zone @ 03/06/25 11:55:23.872
  STEP: Removing pvc created earlier @ 03/06/25 11:56:55.585
  STEP: Removing storage Class created earlier @ 03/06/25 11:56:55.784
  STEP: Deleting workload @ 03/06/25 11:56:55.984
  STEP: Checking that number of Ready nodes is equal to initial @ 03/06/25 11:56:56.185
• [157.554 seconds]
------------------------------
Cluster Autoscaler test testing not able to scale due to excess demand create a pod requiring more resources than a single machine can provide shouldn't scale up and log the error
/Users/i544000/go/src/k8s.io/autoscaler/cluster-autoscaler/integration/integration_test.go:325
  STEP: Checking autoscaler process is running @ 03/06/25 11:58:00.828
  STEP: Deploying the workload @ 03/06/25 11:58:00.828
  STEP: checking that scale up didn't trigger because of no machine satisfying the requirement @ 03/06/25 11:58:01.038
  STEP: Deleting workload @ 03/06/25 11:58:11.093
  STEP: Checking that number of Ready nodes is equal to initial @ 03/06/25 11:58:11.294
• [10.865 seconds]
------------------------------
Cluster Autoscaler test testing CA behaviour when MCM is offline When the available replicas of MCM are zero. The CA should suspend it's operations as long as MCM is offline
/Users/i544000/go/src/k8s.io/autoscaler/cluster-autoscaler/integration/integration_test.go:402
  STEP: Checking autoscaler process is running @ 03/06/25 11:58:11.693
  STEP: Scaling down the MCM @ 03/06/25 11:58:11.693
  STEP: Deleting workload @ 03/06/25 11:58:21.833
  STEP: Checking that number of Ready nodes is equal to initial @ 03/06/25 11:58:22.03
• [10.736 seconds]
------------------------------
[AfterSuite]
/Users/i544000/go/src/k8s.io/autoscaler/cluster-autoscaler/integration/integration_test.go:31
  STEP: Running CleanUp @ 03/06/25 11:58:22.429
  STEP: Deleting workload @ 03/06/25 11:58:22.429
  STEP: Adjusting node groups to initial required size @ 03/06/25 11:58:23.961
  STEP: Deleting workload @ 03/06/25 11:58:24.362
  STEP: Turning nodes present before the tests, back to schedulable @ 03/06/25 11:58:24.557
  STEP: Removing taint(s) from node ip-10-180-24-84.eu-west-1.compute.internal @ 03/06/25 11:58:24.759
  STEP: Removing taint(s) from node ip-10-180-79-175.eu-west-1.compute.internal @ 03/06/25 11:58:25.174
  STEP: Scaling CA back up to 1 in the Shoot namespace @ 03/06/25 11:58:25.592
Scaling Cluster Autoscaler to 1 replicas
[AfterSuite] PASSED [3.813 seconds]
------------------------------

Ran 12 of 12 Specs in 959.884 seconds
SUCCESS! -- 12 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS

Ginkgo ran 1 suite in 16m4.162160584s
Test Suite Passed