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 comments along the lines of "+1", "me too" or "any updates", 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 and review the contribution guide to help.
Terraform Version
1.95
AzureRM Provider Version
4.0.1
Affected Resource(s)/Data Source(s)
azurerm_kubernetes_cluster
Terraform Configuration Files
n/a
Debug Output/Panic Output
N/A
Expected Behaviour
The nat_gateway_profile block implementation done in 2021 in PR #14142
missed the "zone" parameter in the API.
Especially for clusters created in 1 specific zone, you want to be able to control that the managed NAT Gateway is created in the same zone as well. Otherwise you are increasing the risk of an incident, in case the either the zone of the NAT Gateway or the zone of the AKS cluster has an issue.
This --zones parameter seems to do not exist in the ManagedClusterNATGatewayProfile. So probably it is referring to the cluster zones ? But what happens then when we pass --zones 1 2 3 ?
Closing this one because it is not actionable on the Terraform side, given the API limitation. I will be following up with the AKS product team to double check the documentation of the product.
Is there an existing issue for this?
Community Note
Terraform Version
1.95
AzureRM Provider Version
4.0.1
Affected Resource(s)/Data Source(s)
azurerm_kubernetes_cluster
Terraform Configuration Files
n/a
Debug Output/Panic Output
Expected Behaviour
The
nat_gateway_profile
block implementation done in 2021 in PR #14142missed the "zone" parameter in the API.
Product documentation:
https://learn.microsoft.com/en-us/azure/aks/nat-gateway
Actual Behaviour
No response
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: