Skip to content

Commit f9e4fc0

Browse files
committed
fix minor issue reported by the scorecard
1 parent 4e61555 commit f9e4fc0

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/operator-nexus/howto-cluster-manager.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -16,10 +16,10 @@ The Cluster Manager is deployed in the operator's Azure subscription to manage t
1616

1717
## Before you begin
1818

19-
You'll need:
19+
Ensure you have the following information:
2020

2121
- **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).
22-
- **Network Fabric Controller ID** - Network Fabric Controller and Cluster Manager have a 1:1 association. You'll need the resource ID of the Network Fabric Controller associated with the Cluster Manager.
22+
- **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.
2323
- **Log Analytics Workspace ID** - The resource ID of the Log Analytics Workspace used for the logs collection.
2424
- **Azure Region** - The Cluster Manager should be created in the same Azure region as the Network Fabric Controller.
2525
This Azure region should be used in the `Location` field of the Cluster Manager and all associated Operator Nexus instances.
@@ -44,8 +44,8 @@ Some arguments that are available for every Azure CLI command
4444
| managerExtendedLocation | The ExtendedLocation associated with the Cluster Manager |
4545
| managedResourceGroupConfiguration | Information about the Managed Resource Group |
4646
| fabricControllerId | A reference to the Network Fabric Controller that is 1:1 with this Cluster Manager |
47-
| analyticsWorkspaceId | This workspace will be where any logs that 's relevant to the customer will be relayed. |
48-
| clusterVersions[] | List of ClusterAvailableVersions objects. <br> Cluster versions that the manager supports. Will be used as an input in the cluster clusterVersion property. |
47+
| analyticsWorkspaceId | The Log Analytics workspace where logs that are relevant to the customer will be relayed. |
48+
| clusterVersions[] | A list of Cluster versions that the Cluster Manager supports. It is used as an input in the cluster clusterVersion property. |
4949
| provisioningState | Succeeded, Failed, Canceled, Provisioning, Accepted, Updating |
5050
| detailedStatus | Detailed statuses that provide additional information about the status of the Cluster Manager. |
5151
| detailedStatusMessage | Descriptive message about the current detailedStatus.
@@ -62,15 +62,15 @@ The role assignment can be done via Portal:
6262

6363
- Open Azure Portal and locate User-assigned identity in question.
6464
- If you expect multiple managed identities provisioned, the role can be added instead at the resource group or subscription level.
65-
- Under Access control (IAM), click Add new role assignment
65+
- Under `Access control (IAM)`, click Add new role assignment
6666
- Select Role: `Managed Identity Operator`. See the [permissions](https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/identity#managed-identity-operator) that the role provides.
6767
- Assign access to: User, group, or service principal
6868
- Select Member: `AFOI-NC-MGMT-PME-PROD` application
6969
- Review and assign
7070

7171
## Create a Cluster Manager
7272

73-
### Create the Cluster Manager using AZ CLI:
73+
### Create the Cluster Manager using Azure CLI:
7474

7575
Use the `az networkcloud clustermanager create` command to create a Cluster Manager. This command creates a new Cluster Manager or updates the properties of the Cluster Manager if it exists. If you have multiple Azure subscriptions, select the appropriate subscription ID using the [az account set](/cli/azure/account#az-account-set) command.
7676

@@ -108,7 +108,7 @@ az networkcloud clustermanager create \
108108

109109
An alternate way to create a Cluster Manager is with the ARM template editor.
110110

111-
In order to create the cluster this way, you will need to provide a template file (clusterManager.jsonc) and a parameter file (clusterManager.parameters.jsonc).
111+
In order to create the cluster this way, you need to provide a template file (clusterManager.jsonc) and a parameter file (clusterManager.parameters.jsonc).
112112

113113
You can find examples of these two files here:
114114

@@ -280,4 +280,4 @@ az networkcloud clustermanager delete \
280280

281281
## Next steps
282282

283-
After you successfully create an NFC and Cluster Manager, the next step is to create a [Network Fabric](./howto-configure-network-fabric.md).
283+
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

Comments
 (0)