Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The Cluster Manager is deployed in the operator's Azure subscription to manage the lifecycle of Operator Nexus Infrastructure Clusters.
Before you begin
Ensure you have the following information:
- Azure Subscription ID - The Azure subscription ID where Cluster Manager needs to be created (should be the same subscription ID of the Network Fabric Controller).
- Network Fabric Controller ID - Network Fabric Controller and Cluster Manager have a 1:1 association. You need the resource ID of the Network Fabric Controller to be associated with the Cluster Manager.
- Azure Region - The Cluster Manager should be created in the same Azure region as the Network Fabric Controller.
This Azure region should be used in the
Location
field of the Cluster Manager and all associated Operator Nexus instances.
Limitations
- Naming - Naming rules can be found here.
Cluster Manager properties
Property Name | Description |
---|---|
Name, ID, location, tags, type | The Name: User friendly name ID: The Resource ID Location: The Azure region where the Cluster Manager is created. Values from: az account list -locations .Tags: The resource tags Type: Microsoft.NetworkCloud/clusterManagers |
managerExtendedLocation | The ExtendedLocation associated with the Cluster Manager |
managedResourceGroupConfiguration | The details of Managed Resource Group that is created for the Cluster Manager to host its internally used resources. |
fabricControllerId | The reference to the Network Fabric Controller that is 1:1 with this Cluster Manager |
clusterVersions[] | The list of Cluster versions that the Cluster Manager supports. It's used as an input in the Cluster clusterVersion property. |
userAssignedIdentity | The details of the User Assigned Managed Identity, if assigned to the Cluster Manager. |
identity | The details of the type of identity assigned to the Cluster Manager. One of: UserAssigned or SystemAssigned. |
provisioningState | The provisioning status of the latest operation on the Cluster Manager. One of: Succeeded, Failed, Provisioning, Accepted, Updating. |
detailedStatus | The detailed statuses that provide additional information about the status of the Cluster Manager. |
detailedStatusMessage | The descriptive message about the current detailed status. |
Cluster Manager Identity
A customer can assign a Managed Identity to a Cluster Manager. Both System-assigned and User-Assigned Managed Identities are supported starting with the 2024-07-01
API version.
If a Cluster Manager is created with the User-assigned managed identity, a customer is required to provision access to that identity for the Nexus platform.
Specifically, Microsoft.ManagedIdentity/userAssignedIdentities/assign/action
permission needs to be added to the User-assigned identity for AFOI-NC-MGMT-PME-PROD
Microsoft Entra ID. It's a known limitation of the platform that will be addressed in the future.
The role assignment can be done via the Azure portal:
- Open Azure portal and locate User-assigned identity in question.
- If you expect multiple managed identities provisioned, the role can be added instead at the resource group or subscription level.
- Under
Access control (IAM)
, click Add new role assignment - Select Role:
Managed Identity Operator
. See the permissions that the role provides. - Assign access to: User, group, or service principal
- Select Member:
AFOI-NC-MGMT-PME-PROD
application - Review and assign
Create a Cluster Manager
Use the below commands to create a Cluster Manager.
Create Cluster Manager with System Assigned Managed Identity:
az networkcloud clustermanager create \
--name "<CLUSTER_MANAGER_NAME>" \
--location "<LOCATION>" \
--fabric-controller-id "<NFC_ID>" \
--managed-resource-group-configuration name="<MRG_NAME>" location="<MRG_LOCATION>" \
--tags <TAG_KEY1>="<TAG_VALUE1>" <TAG_KEY2>="<TAG_VALUE2>" \
--resource-group "<CLUSTER_MANAGER_RG>" \
--mi-system-assigned \
--subscription "<SUB_ID>"
Create Cluster Manager with User Assigned Managed Identity:
az networkcloud clustermanager create \
--name "<CLUSTER_MANAGER_NAME>" \
--location "<LOCATION>" \
--fabric-controller-id "<NFC_ID>" \
--managed-resource-group-configuration name="<MRG_NAME>" location="<MRG_LOCATION>" \
--tags <TAG_KEY1>="<TAG_VALUE1>" <TAG_KEY2>="<TAG_VALUE2>" \
--resource-group "<CLUSTER_MANAGER_RG>" \
--mi-user-assigned "<UAMI_RID>" \
--subscription "<SUB_ID>"
Arguments:
--name
or-n
[Required] - The name of the Cluster Manager.--resource-group
or-g
[Required] - The name of resource group. You can configure the default resource group usingaz configure --defaults group=<name>
.--fabric-controller-id
[Required] - The resource ID of the Network Fabric Controller that is associated with the Cluster Manager.--location
or-l
- The Azure region where the Cluster Manager is created. Values from:az account list -locations
. You can configure the default location usingaz configure --defaults location="<LOCATION>"
.--managed-resource-group-configuration
- The configuration of the managed resource group associated with the resource.- Usage:
--managed-resource-group-configuration location=XX name=XX
- location: The region of the managed resource group. If not specified, the region of the parent resource is chosen.
- name: The name for the managed resource group. If not specified, a unique name is automatically generated.
- Usage:
wait
/--no-wait
- Wait for command to complete or don't wait for the long-running operation to finish.--tags
- Space-separated tags: key[=value] [key[=value]...]. Use '' to clear existing tags.--subscription
- Name or ID of subscription. You can configure the default subscription usingaz account set -s NAME_OR_ID
.--mi-system-assigned
- Enable System-assigned managed identity. One of--mi-user-assigned
or--mi-system-assigned
can be used at a time.--mi-user-assigned
- The resource ID of the user-assigned managed identity to be added. One of--mi-user-assigned
or--mi-system-assigned
can be used at a time. Cluster Managers only support one user-assigned managed identity.--if-match
/if-none-match
- Specify the last-seen ETag value to prevent accidentally overwriting concurrent changes. The ETag is returned as the resource property once the resource is created and can be used on the update operations.
Common arguments that are available for every Azure CLI command:
--debug
- prints detailed information about CLI execution that is used for debugging purposes. If you find a bug, provide output generated with the--debug
flag on when submitting a bug report.--output
or-o
- specifies the output format. The available output formats are Json, Jsonc (colorized JSON), tsv (Tab-Separated Values), table (human-readable ASCII tables), and yaml. By default the CLI outputs JSON.--query
- uses the JMESPath query language to filter the output returned from Azure services.
List/show Cluster Managers
List and show commands are used to get a list of existing Cluster Managers or the properties of a specific Cluster Manager.
This command lists the Cluster Managers in the specified Resource group.
az networkcloud clustermanager list --resource-group "<CLUSTER_MANAGER_RG>" --subscription "<SUB_ID>"
This command lists the Cluster Managers in the specified subscription.
az networkcloud clustermanager list --subscription "<SUB_ID>"
This command shows the properties of the specified Cluster Manager.
az networkcloud clustermanager show \
--name "<CLUSTER_MANAGER_NAME>" \
--resource-group "<CLUSTER_MANAGER_RG>" \
--subscription "<SUB_ID>"
Update Cluster Manager
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.
This command updates the Cluster Managers in the specified Resource group.
az networkcloud clustermanager update \
--name "<CLUSTER_MANAGER_NAME>" \
--tags <TAG_KEY1>="<TAG_VALUE1>" <TAG_KEY2>="<TAG_VALUE2>" \
--resource-group "<CLUSTER_MANAGER_RG>" \
--subscription "<SUB_ID>"
The Cluster Manager identity can be managed via CLI using az networkcloud clustermanager identity
sub commands.
This command shows the currently assigned identities.
az networkcloud clustermanager identity show \
--name "<CLUSTER_MANAGER_NAME>" \
--resource-group "<CLUSTER_MANAGER_RG>" \
--subscription "<SUB_ID>"
This command adds a user-assigned identity.
az networkcloud clustermanager identity assign \
--name "<CLUSTER_MANAGER_NAME>" \
--resource-group "<CLUSTER_MANAGER_RG>" \
--subscription "<SUB_ID>" \
--mi-user-assigned "<UAMI_RESOURCE_ID>"
This command adds a system-assigned identity.
az networkcloud clustermanager identity assign \
--name "<CLUSTER_MANAGER_NAME>" \
--resource-group "<CLUSTER_MANAGER_RG>" \
--subscription "<SUB_ID>" \
--mi-system-assigned
This command removes the user-assigned identity.
az networkcloud clustermanager identity remove \
--name "<CLUSTER_MANAGER_NAME>" \
--resource-group "<CLUSTER_MANAGER_RG>" \
--subscription "<SUB_ID>" \
--mi-user-assigned "<UAMI_RESOURCE_ID>"
This command removes the system-assigned identity.
az networkcloud clustermanager identity remove \
--name "<CLUSTER_MANAGER_NAME>" \
--resource-group "<CLUSTER_MANAGER_RG>" \
--subscription "<SUB_ID>" \
--mi-system-assigned
Delete Cluster Manager
This command is used to Delete the provided Cluster Manager.
Warning
A Cluster Manager that has any existing associated Clusters will fail to delete. All existing associated Clusters have to be deleted before deleting the Cluster Manager.
az networkcloud clustermanager delete \
--name "<CLUSTER_MANAGER_NAME>" \
--resource-group "<CLUSTER_MANAGER_RG>" \
--subscription "<SUB_ID>"
Note
As best practice, wait 20 minutes after deleting a Cluster Manager before trying to create a new Cluster Manager with the same name.
Next steps
After you successfully created the Network Fabric Controller and the Cluster Manager, the next step is to create a Network Fabric.