You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/operator-nexus/quickstarts-tenant-workload-deployment.md
+1-10Lines changed: 1 addition & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -485,14 +485,6 @@ az hybridaks vnet create \
485
485
486
486
This section describes how to create an AKS-Hybrid cluster
487
487
488
-
You should have the following information already:
489
-
490
-
- AKS-Hybrid vNET network ARM resource IDs
491
-
- Azure Subscription ID
492
-
- Custom location ARM resource ID
493
-
- AAD admin group object IDs
494
-
- Get the available zones to deploy the AKS-Hybird cluster via `az networkcloud cluster show -g <Nexus on-prem cluster RG> --name <Nexus on-prem cluster name> --query computeRackDefinitions[*].availabilityZone`
495
-
496
488
```azurecli
497
489
az hybridaks create \
498
490
-n <aks-hybrid cluster name> \
@@ -506,8 +498,7 @@ You should have the following information already:
506
498
--control-plane-count <count> \
507
499
--location <dc-location> \
508
500
--node-count <worker node count> \
509
-
--node-vm-size <Operator Nexus SKU> \
510
-
--zones <comma separated list of availability zones>
501
+
--node-vm-size <Operator Nexus SKU>
511
502
```
512
503
513
504
After a few minutes, the command completes and returns JSON-formatted information about the cluster.
0 commit comments