search

kubernetes / autoscaler

Autoscaling components for Kubernetes
Apache License 2.0
8.11k stars 3.98k forks source link

Failed logs for other ASGs available in EKS. #6323

Closed uzayr closed 1 week ago

uzayr commented 12 months ago

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):

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 commented 12 months ago

/area provider/aws

yongzhang commented 10 months ago

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 commented 5 months ago

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

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

You can:

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

/lifecycle stale

Shubham82 commented 5 months ago

/remove-lifecycle stale

k8s-triage-robot commented 2 months ago

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

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

You can:

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

/lifecycle stale

k8s-triage-robot commented 1 month ago

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

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

You can:

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

/lifecycle rotten

k8s-triage-robot commented 1 week ago

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

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 1 week ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/autoscaler/issues/6323#issuecomment-2480982771): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.