remove bad attribute from AKS profiles.

Author: phealy

articles/aks/cluster-configuration.md

@@ -302,8 +302,7 @@ The following deployment uses the ARM template `azurelinuxaksarm.json`.
             "count": "[parameters('agentCount')]",
             "vmSize": "[parameters('agentVMSize')]",
             "osType": "[parameters('osType')]",
-            "osSKU": "[parameters('osSKU')]",
-            "storageProfile": "ManagedDisks"
+            "osSKU": "[parameters('osSKU')]"
           }
         ],
         "linuxProfile": {

articles/aks/keda-deploy-add-on-arm.md

@@ -99,7 +99,6 @@ The following snippet is a sample deployment that creates a cluster with KEDA en
                         "enableAutoScaling": false,
                         "vmSize": "Standard_D2S_v5",
                         "osType": "Linux",
-                        "storageProfile": "ManagedDisks",
                         "type": "VirtualMachineScaleSets",
                         "mode": "System",
                         "maxPods": 110,
@@ -164,4 +163,4 @@ To learn more, view the [upstream KEDA docs][keda].
 [kubectl]: https://kubernetes.io/docs/reference/kubectl/
 [keda-scalers]: https://keda.sh/docs/scalers/
 [keda-sample]: https://github.com/kedacore/sample-dotnet-worker-servicebus-queue
-[keda]: https://keda.sh/docs/2.12/
+[keda]: https://keda.sh/docs/2.12/

articles/aks/manage-node-pools.md

@@ -499,7 +499,6 @@ When you use an Azure Resource Manager template to create and manage resources,
                     "count": "[variables('agentPoolProfiles').agentCount]",
                     "vmSize": "[variables('agentPoolProfiles').agentVmSize]",
                     "osType": "[variables('agentPoolProfiles').osType]",
-                    "storageProfile": "ManagedDisks",
                     "type": "VirtualMachineScaleSets",
                     "vnetSubnetID": "[variables('agentPoolProfiles').vnetSubnetId]",
                     "orchestratorVersion": "1.15.7"

articles/aks/scale-cluster.md

@@ -36,7 +36,6 @@ Review the [AKS service quotas and limits][service-quotas] to ensure your cluste
         "name": "nodepool1",
         "osDiskSizeGb": 30,
         "osType": "Linux",
-        "storageProfile": "ManagedDisks",
         "vmSize": "Standard_DS2_v2"
       }
     ]
@@ -61,7 +60,6 @@ Review the [AKS service quotas and limits][service-quotas] to ensure your cluste
           "name": "nodepool1",
           "osDiskSizeGb": 30,
           "osType": "Linux",
-          "storageProfile": "ManagedDisks",
           "vmSize": "Standard_DS2_v2",
           "vnetSubnetId": null
         }

articles/aks/tutorial-kubernetes-scale.md

@@ -160,7 +160,6 @@ The following example increases the number of nodes to three in the Kubernetes c
         "osDiskSizeGb": null,
         "osType": "Linux",
         "ports": null,
-        "storageProfile": "ManagedDisks",
         "vmSize": "Standard_D2_v2",
         "vnetSubnetId": null
       }

articles/aks/tutorial-kubernetes-upgrade-cluster.md

@@ -146,7 +146,6 @@ You can either [manually upgrade your cluster](#manually-upgrade-cluster) or [co
           "maxPods": 110,
           "name": "nodepool1",
           "osType": "Linux",
-          "storageProfile": "ManagedDisks",
           "vmSize": "Standard_DS1_v2",
         }
       ],