You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
Provider v3.47.0 added support for expanding the default nodepool by changing VM size via #20628. However, this does not support changing other typically optional parameters, such as os_disk_size_gb, which may differ for a specific VM SKU and might need to be changed for other SKUs (for instance, when changing Standard_D8as_v4 to Standard_D4as_v4.
As we now have the ability to swap the default pool through a temporary pool, can this mechanism be used to modify these parameters that typically require recreating the cluster, or managing the change externally via Azure CLI and then importing the new state?
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Is there an existing issue for this?
Community Note
Description
Provider v3.47.0 added support for expanding the default nodepool by changing VM size via #20628. However, this does not support changing other typically optional parameters, such as
os_disk_size_gb
, which may differ for a specific VM SKU and might need to be changed for other SKUs (for instance, when changingStandard_D8as_v4
toStandard_D4as_v4
.As we now have the ability to swap the default pool through a temporary pool, can this mechanism be used to modify these parameters that typically require recreating the cluster, or managing the change externally via Azure CLI and then importing the new state?
New or Affected Resource(s)/Data Source(s)
azurerm_kubernetes_cluster
Potential Terraform Configuration
References
#7093
#20628
#21859 is related but applies to additional nodepools
The text was updated successfully, but these errors were encountered: