Open cpinjani opened 1 month ago
It doesn't make sense to me to exactly replicate the availability zone behavior from the old UI in the new UI because the region selection behavior is not the same. In the old UI the availability zone inputs are not even visible until the user has confirmed their region choice; as far as the user is concerned, availability zones have not been configured at all, so when the UI changes them under the hood, to the user the cluster has not changed.
In the new UI, users see availability zones at the same time that they're selecting a region. They can even alter availability zones then change regions. If we replicated the old UI's behavior here we actually would be altering the cluster's configuration without the user's awareness. I think it's better UX to show them what they should change and make them remove availability zones themselves. Particularly given that azure advises against using clusters without availability zones, it's beneficial to ensure that the user is aware that that is what they're doing.
Nodepool2: (AZ are auto-disabled)
Setup Rancher - v2.9.1
Describe the bug [v2.9] AKS - Availability Zones on Nodepools must be disabled if Region without AZ is selected for provisioning.
To Reproduce
Screenshots
On 2.8, AZ are auto-disabled:
2.9.1: