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/howto-cluster-manager.md
-23Lines changed: 0 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,8 +14,6 @@ ms.custom: devx-track-azurecli
14
14
15
15
The Cluster Manager is deployed in the operator's Azure subscription to manage the lifecycle of Operator Nexus Infrastructure Clusters.
16
16
17
-
---
18
-
19
17
## Before you begin
20
18
21
19
Ensure you have the following information:
@@ -25,13 +23,9 @@ Ensure you have the following information:
25
23
-**Azure Region** - The Cluster Manager should be created in the same Azure region as the Network Fabric Controller.
26
24
This Azure region should be used in the `Location` field of the Cluster Manager and all associated Operator Nexus instances.
27
25
28
-
---
29
-
30
26
## Limitations
31
27
-**Naming** - Naming rules can be found [here](../azure-resource-manager/management/resource-name-rules.md#microsoftnetworkcloud).
32
28
33
-
---
34
-
35
29
## Cluster Manager properties
36
30
37
31
| Property Name | Description |
@@ -46,7 +40,6 @@ This Azure region should be used in the `Location` field of the Cluster Manager
46
40
| provisioningState | The provisioning status of the latest operation on the Cluster Manager. One of: Succeeded, Failed, Provisioning, Accepted, Updating. |
47
41
| detailedStatus | The detailed statuses that provide additional information about the status of the Cluster Manager. |
48
42
| detailedStatusMessage | The descriptive message about the current detailed status. |
49
-
---
50
43
51
44
## Cluster Manager Identity
52
45
@@ -65,8 +58,6 @@ The role assignment can be done via the Azure portal:
Use the below commands to create a Cluster Manager.
@@ -181,8 +172,6 @@ You can find examples of these two files here:
181
172
1. Make sure all Instance Details are correct.
182
173
1. Click Review + create.
183
174
184
-
---
185
-
186
175
## List/show Cluster Managers
187
176
188
177
List and show commands are used to get a list of existing Cluster Managers or the properties of a specific Cluster Manager.
@@ -234,8 +223,6 @@ This command shows the properties of the specified Cluster Manager in JSON forma
234
223
235
224
To view Cluster Managers, use Portal, CLI, or PowerShell.
236
225
237
-
---
238
-
239
226
## Update Cluster Manager
240
227
241
228
This command is used to patch properties of the provided Cluster Manager, or update the tags assigned to the Cluster Manager. Properties and tag updates can be done independently.
The template used for creation can also be used to update the Cluster Manager.
281
268
282
-
---
283
-
284
269
## Cluster Manager identity
285
270
286
271
The Cluster Manager identity can be managed via CLI using `az networkcloud clustermanager identity` sub commands.
@@ -334,8 +319,6 @@ az networkcloud clustermanager identity remove \
334
319
--mi-system-assigned
335
320
```
336
321
337
-
---
338
-
339
322
## Delete Cluster Manager
340
323
341
324
This command is used to Delete the provided Cluster Manager.
@@ -365,17 +348,11 @@ To delete the Cluster Manager, use Portal, CLI, or PowerShell.
365
348
>[!NOTE]
366
349
>As best practice, wait 20 minutes after deleting a Cluster Manager before trying to create a new Cluster Manager with the same name.
367
350
368
-
---
369
-
370
351
## Next steps
371
352
372
353
After you successfully created the Network Fabric Controller and the Cluster Manager, the next step is to create a [Network Fabric](./howto-configure-network-fabric.md).
0 commit comments