Skip to content

Commit 7273408

Browse files
authored
Added a prereq step to get the available zones
1 parent 2745085 commit 7273408

File tree

1 file changed

+15
-1
lines changed

1 file changed

+15
-1
lines changed

articles/operator-nexus/quickstarts-tenant-workload-prerequisites.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,20 @@ You need:
4949
- your Azure account and the subscription ID of Operator Nexus cluster deployment
5050
- the `custom location` resource ID of your Operator Nexus cluster
5151

52+
## AKS-Hybrid availablity zone
53+
`--zones` option in `az hybridaks create` or `az hybridaks nodepool add` can be used to distribute the AKS-Hybrid clusters across different zones for better fault tolerance and performance. By specifying the --zones option when creating a AKS-Hybrid cluster, you can ensure that the cluster is scheduled onto a nodes in a specific rack or distributed evenly across multiple racks for better resource utilization and fault tolerance.
54+
55+
In case you don't specify a zone while creating a AKS-Hybrid cluster through the --zones option, Operator Nexus platform will automatically implement a default anti-affinity rule. This anti-affinity rule aims to prevent scheduling the cluster VM on a node that already has a VM from the same cluster, but it is a best-effort approach and cannot guarantee it.
56+
57+
To obtain the list of available zones in the given Operator Nexus instance, you can use the following command.
58+
59+
```azurecli
60+
az networkcloud cluster show \
61+
--resource-group <Operator Nexus on-prem cluster Resource Group> \
62+
--name <Operator Nexus on-prem cluster name> \
63+
--query computeRackDefinitions[*].availabilityZone
64+
```
65+
5266
### Review Azure container registry
5367

5468
[Azure Container Registry](../container-registry/container-registry-intro.md) is a managed registry service to store and manage your container images and related artifacts.
@@ -133,4 +147,4 @@ This VM image build procedure is derived from [kubevirt](https://kubevirt.io/use
133147
To deploy your workloads, you need:
134148

135149
- to create resource group or find a resource group to use for your workloads
136-
- the network fabric resource ID to create isolation-domains.
150+
- the network fabric resource ID to create isolation-domains.

0 commit comments

Comments
 (0)