-
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
Azure: "AKS" vmType no longer works #6190
Labels
area/provider/azure
Issues or PRs related to azure provider
kind/bug
Categorizes issue or PR as related to a bug.
Comments
/assign |
Here are the relevant log messages that indicate that the cluster-autoscaler runtime is not able to properly bootstrap itself for node pools w/ the "AKS" vmType:
|
@gandhipr let me know if there's anything else we can document as part of proving that this doesn't work Also let me know if my testing is incorrect. Thanks! |
/area provider/azure |
k8s-ci-robot
added
the
area/provider/azure
Issues or PRs related to azure provider
label
Nov 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/provider/azure
Issues or PRs related to azure provider
kind/bug
Categorizes issue or PR as related to a bug.
Which component are you using?:
cluster-autoscaler
What version of the component are you using?:
Component version: 1.27.2
What k8s version are you using (
kubectl version
)?:kubectl version
OutputWhat environment is this in?:
Azure AKS
What did you expect to happen?:
I expect to be able to install the cluster-autoscaler runtime w/ a vmType configuration of "AKS" on an AKS cluster
What happened instead?:
Configured node pools are not identified for proper scaling
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
The text was updated successfully, but these errors were encountered: