Support for new-pod-scale-up for autoscaler profile on AKS

[alk-rniveau]

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

The new hidden parameter for autoscaler profile new-pod-scale-up (Azure/AKS#1716) is not yet supported by azurerm provider.

Do you plan to do it ?

New or Affected Resource(s)

azurerm_kubernetes_cluster

Potential Terraform Configuration

 auto_scaler_profile = {
    balance_similar_node_groups      = false
    max_graceful_termination_sec     = 600
    scale_down_delay_after_add       = "10m"
    scale_down_delay_after_delete    = "10s"
    scale_down_delay_after_failure   = "3m"
    scan_interval                    = "10s"
    scale_down_unneeded              = "1m"
    scale_down_unready               = "20m"
    scale_down_utilization_threshold = "0.5"
    new_pod_scale_up                 = "5m"
  }

[dstrebel]

I can create a PR for this.

[tillepille]

@dstrebel @alk-rniveau
It would be awesome if the azurerm_kubernetes_cluster_node_pool resource would support this as well!

[ghost]

This has been released in version 2.44.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.44.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!