Merge pull request #300138 from matternst7258/matternst7258/storage-name

Update storageApplianceName to new tag, nexusSharedStorageApplianceName

Author: prmerger-automator[bot]

articles/operator-nexus/cluster-parameters-jsonc-example.md

@@ -5,7 +5,7 @@ author: bartpinto
 ms.author: bpinto
 ms.service: azure-operator-nexus
 ms.topic: how-to
-ms.date: 03/31/2025
+ms.date: 05/22/2025
 ms.custom: template-how-to, devx-track-arm-template
 ---
 

articles/operator-nexus/concepts-storage-kubernetes.md

@@ -5,7 +5,7 @@ author: pjw711
 ms.author: peterwhiting
 ms.service: azure-operator-nexus
 ms.topic: conceptual
-ms.date: 01/06/2025
+ms.date: 05/22/2025
 ms.custom: template-concept
 ---
 

articles/operator-nexus/concepts-storage-multiple-appliances.md

@@ -5,7 +5,7 @@ author: pjw711
 ms.author: peterwhiting
 ms.service: azure-operator-nexus
 ms.topic: conceptual
-ms.date: 03/12/2025
+ms.date: 05/22/2025
 ms.custom: template-concept
 ---
 
@@ -89,11 +89,11 @@ Azure Operator Nexus provides a shared filesystem storage solution for container
 
 You can create the shared storage service on either storage appliance when the CSN is created. All nexus-shared PVCs using that shared storage service consume storage from the storage appliance backing the shared service. The configuration applies to all nexus-shared PVCs using the shared storage service provided by the CSN. All nexus-shared PVCs using the same shared storage service use the same storage appliance.
 
-The `nexusSharedStorageApplianceName` Azure resource tag controls which storage appliance is used to back the shared storage service. See [Prerequisites for deploying tenant workloads](./quickstarts-tenant-workload-prerequisites.md#create-a-cloud-services-network) for instructions on creating the shared storage service on a specific storage appliance.
+The `storageApplianceName` Azure resource tag controls which storage appliance is used to back the shared storage service. See [Prerequisites for deploying tenant workloads](./quickstarts-tenant-workload-prerequisites.md#create-a-cloud-services-network) for instructions on creating the shared storage service on a specific storage appliance.
 
 If no storage appliance configuration is provided at CSN creation time, the shared storage service uses the first storage appliance. If the configuration is present but doesn't match a storage appliance then the CSN creation will fail.
 
-Subsequent updates to the `nexusSharedStorageApplianceName` Azure resource tag have no effect. There is no support for moving the shared filesystem storage solution between storage appliances after initial deployment.
+Subsequent updates to the `storageApplianceName` Azure resource tag have no effect. There is no support for moving the shared filesystem storage solution between storage appliances after initial deployment.
 
 #### Nexus-shared limitations
 

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

@@ -5,7 +5,7 @@ author: bartpinto
 ms.author: bpinto
 ms.service: azure-operator-nexus
 ms.topic: how-to
-ms.date: 03/31/2025
+ms.date: 05/22/2025
 ms.custom: template-how-to, devx-track-azurecli
 ---
 

articles/operator-nexus/quickstarts-tenant-workload-prerequisites.md

@@ -5,7 +5,7 @@ author: dramasamy
 ms.author: dramasamy
 ms.service: azure-operator-nexus
 ms.topic: how-to
-ms.date: 01/25/2023
+ms.date: 05/22/2023
 ms.custom: template-how-to-pattern, devx-track-azurecli, devx-track-azurepowershell
 ---
 
@@ -185,7 +185,7 @@ Deployments with multiple storage appliances support selecting the storage appli
     --extended-location name="<ClusterCustomLocationId >" type="CustomLocation" \
     --location "<ClusterAzureRegion>" \
     --additional-egress-endpoints "[{\"category\":\"<YourCategory >\",\"endpoints\":[{\"<domainName1 >\":\"< endpoint1 >\",\"port\":<portnumber1 >}]}]"
-    --tags "nexusSharedStorageApplianceName": "<YourStorageApplianceName>""
+    --tags "storageApplianceName": "<YourStorageApplianceName>""
 ```
 
 ### [Azure PowerShell](#tab/azure-powershell)
@@ -201,7 +201,7 @@ $additionalEgressEndpoint = New-AzNetworkCloudEgressEndpointObject `
   -Category "YourCategory" `
   -Endpoint $endpointList
 $endpointEgressList+= $additionalEgressEndpoint
-$tags @{"nexusSharedStorageApplianceName"="<YourStorageApplianceName>"}
+$tags @{"storageApplianceName"="<YourStorageApplianceName>"}
 
 New-AzNetworkCloudServicesNetwork -CloudServicesNetworkName "<YourCloudServicesNetworkName>" `
 -ResourceGroupName "<YourResourceGroupName>" `

articles/operator-nexus/troubleshoot-multiple-storage-appliances.md

@@ -4,7 +4,7 @@ description: Troubleshooting common issues with multiple Storage Appliances
 ms.service: azure-operator-nexus
 ms.custom: troubleshooting
 ms.topic: troubleshooting
-ms.date: 08/12/2024
+ms.date: 05/22/2024
 ms.author: peterwhiting
 author: pjw711
 ---
@@ -51,10 +51,10 @@ The `storageApplianceName` annotation must match one of the storage appliances i
 
 ## Cloud Service Network (CSN) fails to create
 
-A CSN fails to create if the `nexusSharedStorageApplianceName` Azure resource tag is present but doesn't match the Azure Resource name of a storage appliance managed by the Nexus Cluster. You can check that the `nexusSharedStorageApplianceName` Azure resource tag is correct by:
+A CSN fails to create if the `storageApplianceName` Azure resource tag is present but doesn't match the Azure Resource name of a storage appliance managed by the Nexus Cluster. You can check that the `storageApplianceName` Azure resource tag is correct by:
 
 1. Opening the Cluster (Operator Nexus) resource in the Azure portal
 1. Clicking on Rack definitions in the resource menu.
 1. Navigating to the aggregator rack and selecting Storage Appliance definitions.
 
-The `nexusSharedStorageApplianceName` Azure resource tag must match one of the storage appliances in the Storage Appliance definitions list. You must delete the CSN and recreate it with the correct Azure Resource tag to resolve this issue.
+The `storageApplianceName` Azure resource tag must match one of the storage appliances in the Storage Appliance definitions list. You must delete the CSN and recreate it with the correct Azure Resource tag to resolve this issue.