Support for max_surge parameter on azurerm_kubernetes_cluster_node_pool

[jmcshane]

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

Support the max surge parameter for upgrading node pools. Available in sdk-for-go in the 2020-04-01 API version here.

New or Affected Resource(s)

• azurerm_kubernetes_cluster_node_pool

Potential Terraform Configuration

resource "azurerm_kubernetes_cluster_node_pool" "example" {
  name                  = "internal"
  kubernetes_cluster_id = azurerm_kubernetes_cluster.example.id
  vm_size               = "Standard_DS2_v2"
  node_count            = 1
  
  upgrade_settings {
    max_surge = 2
    ## or max_surge = 50%
  }
  tags = {
    Environment = "Production"
  }
}

References

• https://docs.microsoft.com/en-us/azure/aks/upgrade-cluster#set-up-the-preview-feature-for-customizing-node-surge-upgrade

[shapeofarchitect]

Can we please , please start to merge these important Pull Requests ?

[ghost]

This has been released in version 2.48.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.48.0"
}
# ... other configuration ...

[ghost]

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!