Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: Need AvailabilityZone parameter for New-AzAksCluster #18658

Closed
Xingbin-Li opened this issue Jun 22, 2022 · 1 comment · Fixed by #18733
Closed

[Feature]: Need AvailabilityZone parameter for New-AzAksCluster #18658

Xingbin-Li opened this issue Jun 22, 2022 · 1 comment · Fixed by #18733
Assignees
Labels
AKS customer-reported feature-request This issue requires a new behavior in the product in order be resolved.

Comments

@Xingbin-Li
Copy link

Description of the new feature

As per official AKS document, it is stated that

The control plane components such as etcd or the API are spread across the available zones in the region if you define the --zones parameter at cluster creation time.

So we need AvailabilityZone parameter for New-AzAksCluster as well in order to spread control plane across the available zones when use powershell commands to create the cluster.

Proposed implementation details (optional)

No response

@Xingbin-Li Xingbin-Li added feature-request This issue requires a new behavior in the product in order be resolved. needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Jun 22, 2022
@ghost ghost added customer-reported and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Jun 22, 2022
@dingmeng-xue
Copy link
Member

@wyunchi-ms , please help to look into this requirement.

@wyunchi-ms wyunchi-ms linked a pull request Jun 27, 2022 that will close this issue
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AKS customer-reported feature-request This issue requires a new behavior in the product in order be resolved.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants