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
I expect the cluster to be recreated since availability zones cannot be changed without destroying the cluster. It should warn about the cluster recreation and create the new with the availability zones. Azure does not support changing the availability zones of a created cluster.
See limitations in the Availability Zones for AKS documentation of Microsoft here.
Actual Behavior
Terraform detect changes that could be applied to the cluster without recreating it (which is incorrect, regarding the docs).
Due to this incorrect change detection, it attempts to apply impossible changes and it results either in timeout or applying the changes without doing nothing.
Steps to Reproduce
terraform apply of the config file attached.
It detect changes as the attached output.
The apply sometimes results in a timeout or in "changes applied" (but there are no changes), it detect changes in subsequent terraform apply.
Important Factoids
No important Factoids.
References
No references.
The text was updated successfully, but these errors were encountered:
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!
ghost
locked as resolved and limited conversation to collaborators
Dec 7, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform (and AzureRM Provider) Version
Terraform v0.12.28
provider.azurerm v2.18.0
Affected Resource(s)
azurerm_kubernetes_cluster
Terraform Configuration Files
Debug Output
Panic Output
No panic output.
Expected Behavior
I expect the cluster to be recreated since availability zones cannot be changed without destroying the cluster. It should warn about the cluster recreation and create the new with the availability zones. Azure does not support changing the availability zones of a created cluster.
See limitations in the Availability Zones for AKS documentation of Microsoft here.
Actual Behavior
Terraform detect changes that could be applied to the cluster without recreating it (which is incorrect, regarding the docs).
Due to this incorrect change detection, it attempts to apply impossible changes and it results either in timeout or applying the changes without doing nothing.
Steps to Reproduce
terraform apply
of the config file attached.terraform apply
.Important Factoids
No important Factoids.
References
No references.
The text was updated successfully, but these errors were encountered: