Closed zioproto closed 1 week ago
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.
It might be the documentation that is misleading: https://learn.microsoft.com/en-us/azure/aks/nat-gateway#create-an-aks-cluster-with-a-managed-nat-gateway
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
Debug Output/Panic Output
Expected Behaviour
The
nat_gateway_profile
block implementation done in 2021 in PR https://github.com/hashicorp/terraform-provider-azurerm/pull/14142 missed 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