Failed logs for other ASGs available in EKS.

[uzayr]

What version of the component are you using? v1.28.0

EKS Version: 1.28

Error logs clusterstate.go:1033] Failed to check cloud provider has instance for ip-xxx-xx-xx-xx.ec2.internal: node is not present in aws: could not find instance {aws:///us-east-1c/i-xxxxxxxxxxxxxxxx i-xxxxxxxxxxxxxxx}

Scenario As per multiple cluster-autoscaler deployment in a cluster, each namespace has its own cluster-autoscaler deployment. Each namespaced autoscaler is associated with their ASG. But autoscaler is fetching all nodes available in EKS and throws failed log msgs in logs for other ASG's nodes too.

Problem Not filtering out nodes with all given tags to asg:tag. Still checking all the nodes available in the cluster and logging warning msgs.

How to reproduce it (as minimally and precisely as possible):

• Do multiple deployments of cluster-autoscaler in a cluster.
• Keep each cluster-autoscaler to manage specific ASG with tag filtering using --node-group-auto-discovery=asg:tag=.

Note: I've tested only v1.27.2 and v1.28.0 version and it's happening to both versions. But v1.26.1 version is working fine.

[Shubham82]

/area provider/aws

[yongzhang]

Same issue on 1.28, I have single cluster-autoscaler but multiple ASGs. These nodes in the error logs are not in the ASG for auto discovering.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Shubham82]

/remove-lifecycle stale