-
Notifications
You must be signed in to change notification settings - Fork 4k
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
AKS cluster-autoscaler stucks in "Initializing". #2236
Comments
Here is the root cause of this issue.
The controller doesn't set
So every |
k8s-ci-robot
added a commit
that referenced
this issue
Aug 22, 2019
[CA][Azure] Ignore nodes that have no ProviderID. (#2236)
feiskyer
pushed a commit
to feiskyer/autoscaler
that referenced
this issue
Sep 12, 2019
Signed-off-by: Masaki Muranaka <[email protected]>
feiskyer
pushed a commit
to feiskyer/autoscaler
that referenced
this issue
Sep 12, 2019
Signed-off-by: Masaki Muranaka <[email protected]>
feiskyer
pushed a commit
to feiskyer/autoscaler
that referenced
this issue
Sep 12, 2019
Signed-off-by: Masaki Muranaka <[email protected]>
feiskyer
pushed a commit
to feiskyer/autoscaler
that referenced
this issue
Sep 12, 2019
Signed-off-by: Masaki Muranaka <[email protected]>
This was referenced Sep 12, 2019
mikkeloscar
pushed a commit
to zalando-incubator/autoscaler
that referenced
this issue
Sep 4, 2020
Signed-off-by: Masaki Muranaka <[email protected]>
mikkeloscar
pushed a commit
to zalando-incubator/autoscaler
that referenced
this issue
Aug 24, 2022
Signed-off-by: Masaki Muranaka <[email protected]>
tim-smart
pushed a commit
to arisechurch/autoscaler
that referenced
this issue
Nov 22, 2022
Signed-off-by: Masaki Muranaka <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On AKS (not with VMSS) 1.14.3, cluster-autoscaler stucks under "Initializing" state.
Nodes information on my node is:
After inspecting code, I convinced it is caused only in case Virtual Kubelet was deployed.
I'll send the PR for fixing this soon.
The text was updated successfully, but these errors were encountered: