Skip to content

Commit 169fece

Browse files
committed
Minor updates for Cluster deploy
1 parent 0776e30 commit 169fece

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ You can find examples for an 8-Rack 2M16C SKU cluster using these two files:
147147

148148
### Cluster validation
149149

150-
A successful Operator Nexus Cluster creation results in the creation of an Azure Kubernetes Service (AKS) cluster
150+
A successful Operator Nexus Cluster creation results in the creation of a Azure resource
151151
inside your subscription. The cluster ID, cluster provisioning state, and
152152
deployment state are returned as a result of a successful `cluster create`.
153153

@@ -271,6 +271,7 @@ metal machines that failed the hardware validation (for example, `COMP0_SVR0_SER
271271
```
272272

273273
See the article [Tracking Asynchronous Operations Using Azure CLI](./howto-track-async-operations-cli.md) for another example.
274+
See the article [Troubleshoot BMM provisioning](./troubleshoot-bare-metal-machine-provisioning.md) for more information that may be helpful when specific machines fail validation or deployment.
274275

275276
## Cluster deployment validation
276277

0 commit comments

Comments
 (0)