Skip to content
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

Support for changing AKS default node pool params without recreating the cluster #21881

Closed
1 task done
adityasundaramurthy-maersk opened this issue May 22, 2023 · 2 comments · Fixed by #21719
Closed
1 task done

Comments

@adityasundaramurthy-maersk

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • 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?

New or Affected Resource(s)/Data Source(s)

azurerm_kubernetes_cluster

Potential Terraform Configuration

Resource configuration remains unchanged

References

#7093
#20628
#21859 is related but applies to additional nodepools

@aristosvo
Copy link
Collaborator

Hi @adityasundaramurthy-maersk! Thanks for opening this issue.

As far as I know this should be covered by the open PR #21719.

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants