Azure / Azure/AKS

Conflicting documentation on availability zone support for Virtual Machines node pools

Open
#5,911 7 comments 0 reactions 1 assignee Claimed by @dyu1208 View on GitHub
availability zones docs nodepools
Dominant language
TypeScript
Stars
2.1k
Forks
395
Avg merge
4d 15h
Merged PRs (30d)
14

Description

### Documentation conflict

The following AKS documentation pages provide conflicting information about availability zone support for Virtual Machines-based node pools.

The Virtual Machines node pool page states:

> Availability zones aren't supported. If your workload requires zone resiliency, use Virtual Machine Scale Sets node pools.

https://learn.microsoft.com/azure/aks/virtual-machines-node-pools

However, the Automatic Zone Placement page states:

> Automatic zone placement supports creating and updating both Virtual Machine Scale Sets-based and Virtual Machines-based node pools.

https://learn.microsoft.com/azure/aks/configure-automatic-zone-placement

The related AKS issue also describes the feature as supporting VMSS and VMs node pools:

https://github.com/Azure/AKS/issues/5595

### Request

Could you confirm which documentation is correct?

Please update the documentation so that the availability zone support and limitations for Virtual Machines-based node pools are stated consistently.

The `MicrosoftDocs/azure-aks-docs` repository has GitHub Issues disabled, so I am reporting the inconsistency here.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.