-
Notifications
You must be signed in to change notification settings - Fork 459
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 cost analysis add-on [azurerm_kubernetes_cluster] #528
Comments
@fabio-s-franco the link you shared with the GA announcement is for another feature: https://azure.microsoft.com/updates/generally-available-vm-ip-based-load-balancer-in-aks/ The correct link is: |
Status: waiting on Terraform provider feature: hashicorp/terraform-provider-azurerm#23982 |
Ooops, thanks for letting me know @zioproto , copy past problem. I will fix it now |
I could swear that I searched for this issue and couldn't find it. Should I close this one? |
Please keep this issue open. Here we track the Terraform module support. The other issue is for the Terraform provider support. Thanks |
Hi, is there an ETA when the this feature will be added to the next azurerm provider release? |
Please follow this issue hashicorp/terraform-provider-azurerm#23982 @ms-henglu is working on this, and will link the PR implementing that feature on that GitHub issue. I don't have an update on the ETA yet. |
Product is GA: As documented in: |
Hi, do you have any updates of the feature? The other post, hashicorp/terraform-provider-azurerm#23982, seems that was closed automatically. |
Is there an existing issue for this?
Description
GA for AKS cost analysis has been announced, it would be nice to have that in the cluster resource for the provider.
According to the documentation it is just a flag to enable or disable it via CLI. I am not sure how that translates to the API though as I didn't immediately find it.
New or Affected Resource(s)/Data Source(s)
azurerm_kubernetes_cluster
Potential Terraform Configuration
References
No response
The text was updated successfully, but these errors were encountered: