-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Cannot increase maximum size of Azure VMSS #2136
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Why are we limited to 40 VMSS max instances in the terraform config? |
PR pending review here: #2806 |
Including the changes from @georgespatton in #2806 - pushing to that fork broken the PR 🤷♂️ Original PR: --- This should fix #2136 as well as #2624 to follow the Azure documentation here: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/overview Fixes #2136 Fixes #2624
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Community Note
I can't increase the size of an existing VMSS within Azure. It was created via terraform originally. I am using the latest version of terraform. I tried the latest version of provider.azurerm (v1.17.0) with the same behavior.
To reproduce, create an Azure VMSS with terraform with set minimum/maximum/default values. Then increase the maximum setting. It should fail as this does.
The text was updated successfully, but these errors were encountered: