Currently, the implementation of the NodeGroupForNode function in the AliCloudProvider has two caches within autoScalingGroups: instanceToAsg and instancesNotInManagedAsg.

instanceToAsg records instances in Managed ASGs.
instancesNotInManagedAsg records instances not in Managed ASGs.
When an unknown instance is encountered, a regenerateCache is triggered. If it’s determined to be an instance not in a Managed ASG, it’s saved to instancesNotInManagedAsg, avoiding the need to call regenerateCache on subsequent occurrences.

This functionality is correct. However, if a large number of nodes are created via instances not in Managed ASGs, every call to NodeGroupForNode->GetAsgForInstance->FindForInstance will trigger a regenerateCache. If there are a significant number of instances in Managed ASGs at that time, this could lead to frequent calls, each with a considerable time overhead for regenerateCache.

For example, if there are 1000 machines in Managed ASGs and suddenly 2000 instances not in Managed ASGs are added:

UpdateNodes->updateReadinessStats->NodeGroupForNode
This call is executed with every runOnce, and each node invokes NodeGroupForNode once. The 2000 newly added instances not in Managed ASGs will trigger regenerateCache, but it will only count instances in Managed ASGs. However, it will still execute 2000 times.

Assuming each regenerateCache call takes 10 seconds, this function will take:

2000 instances * 10 seconds/instance = 20000 seconds.
This significantly extends the duration of a single runOnce operation. During this period, if new pending pods appear, the Cluster Autoscaler might not function as expected, posing a severe risk.