-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cluster Autoscaler: when the pool size has been scaled down to zero, it will never trigger new scale out. #4805
Comments
See this: #4739 |
So could someone confirm that this issue will be fixed in 8f11490 and resolved in cluster-autoscaler v1.22.0 onwards? |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Which component are you using?: cluster-autoscaler
What version of the component are you using?: Cluster Autoscaler 1.21.1
Component version:
What k8s version are you using (
kubectl version
)?: 1.21.3kubectl version
OutputWhat environment is this in?: Azure VMSS
What did you expect to happen?: The cluster autoscale will make sure the node size will be no less than minimal node count setting.
What happened instead?:
When the pool size has been scaled down to zero, it will never trigger new scale out.
Cluster Autoscaler doesn’t work as expected to:
How to reproduce it (as minimally and precisely as possible):
Scale down the agent pool to zero node, the you can watch its behavior as shown above.
Anything else we need to know?:
The text was updated successfully, but these errors were encountered: