Skip to content

Commit b21d3c5

Browse files
author
manasareddybethi
committed
Add why not to patch the cluster before redfish strings are formed
1 parent 0685768 commit b21d3c5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,8 +39,8 @@ You should create the Network Fabric before this on-premises deployment.
3939
Each Operator Nexus on-premises instance has a one-to-one association
4040
with a Network Fabric.
4141

42-
> [!NOTE]
43-
> After creating the cluster, avoid applying patches to it until the `az networkcloud cluster show` CLI command displays redfish bmcConnectionStrings for the corresponding cluster.
42+
> [!IMPORTANT]
43+
> After creating the cluster, avoid applying patches to it until the `az networkcloud cluster show` CLI command displays redfish bmcConnectionStrings for the corresponding cluster. Patching the cluster before these strings are generated can result in version overrides and the loss of bmcConnectionStrings from the cluster's Custom Resource.
4444
4545
### Create the Cluster using Azure CLI:
4646

0 commit comments

Comments
 (0)