Hi Bramandlapally, Mahesh,It is feasible to add a new node pool specifically aligned to Zones 1 or 3, while keeping your cluster multi-zonal. AKS supports zone-aligned node pools, meaning you can have one node pool dedicated to a specific zone (like Z1 or Z3), while other node pools remain multi-zonal or aligned to other zones.
Zone-aligned Node Pools: Each node pool can be pinned to a specific zone during creation. This ensures only the new GPU node pool is in the supported zone, but the rest of the cluster retains its existing configuration. https://learn.microsoft.com/en-us/azure/aks/reliability-availability-zones-configure
Moving your entire cluster to a single zone is generally not recommended unless all workloads can tolerate reduced high availability.
- Loss of Resilience: Operating in a single zone reduces resiliency. Any outage in that zone will impact your entire cluster.
- High Availability: AKS best practices strongly recommend using multi-zone clusters for mission-critical applications, as zone failure will only impact part of the cluster. If you reconfigure everything to a single zone, a zone-level outage will bring down all workloads.
- Redeploying System Node Pool: If you switch the system node pool (and thus the control plane) to a single zone, this would require re-creating the cluster or significant downtime for migration. Existing resources and state in Zone 2 may be lost unless explicitly backed up and restored.
If you have any further queries, let me know.