You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/service-fabric/how-to-managed-cluster-modify-node-type.md
-60Lines changed: 0 additions & 60 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -298,66 +298,6 @@ To modify the OS image used for a node type using an ARM Template, adjust the `v
298
298
}
299
299
```
300
300
301
-
## Modify disc size on an existing node type
302
-
Service Fabric Managed Clusters enables you to modify the disc size for new nodes in an exsisting node type in place. As you deploy and run your application, load increases or decreases may cause a need to change the disc size on a node type.
303
-
304
-
[!NOTE]
305
-
While Azure is making updates to the node type, other changes cannot be made to the node type. Service Fabric Managed Clusters will spin up new nodes with the new disc size; therefore, the old nodes have to be scaled down. See the below on procedure to scale a node type.
306
-
307
-
### Modify disc size using portal
308
-
In this walkthrough, you will learn how to modify a disc size using portal.
309
-
310
-
1) Log in to [Azure portal](https://portal.azure.com/)
311
-
312
-
2) Navigate to your cluster resource Overview page.
313
-
![Sample Overview page][overview]
314
-
315
-
3) Select `Node Types` under the `Settings` section
316
-
317
-
4) Select `Change size` under the Data disk size
318
-
319
-
5) Pick the size you wish and select ok
320
-
321
-
6) select `Apply` at the bottom and wait for the changes to be applied
322
-
323
-
324
-
### Modify disc size using arm template
325
-
To adjust the disc size for a node type using an ARM Template, adjust the dataDiskSizeGB property with the new value(s) and do a cluster deployment for the setting to take effect. The below sample shows three values being set for a node type.
326
-
327
-
The Service Fabric managed cluster resource apiVersion should be 2021-05-01 or later.
328
-
329
-
```json
330
-
},
331
-
"properties": {
332
-
"isPrimary": true,
333
-
"vmImagePublisher": "MicrosoftWindowsServer",
334
-
"vmImageOffer": "WindowsServer",
335
-
"vmImageSku": "2019-Datacenter",
336
-
"vmImageVersion": "latest",
337
-
"vmSize": "Standard_D2s_v3",
338
-
"vmInstanceCount": 6,
339
-
"dataDiskSizeGB": 256,
340
-
"dataDiskType": "StandardSSD_LRS",
341
-
"dataDiskLetter": "S",
342
-
"placementProperties": {},
343
-
"capacities": {},
344
-
"applicationPorts": {
345
-
"startPort": 20000,
346
-
"endPort": 30000
347
-
},
348
-
"ephemeralPorts": {
349
-
```
350
-
351
-
### Modify disc size using powershell
352
-
353
-
The following example will update and overwrite any existing disc properties for a given node type.
354
-
355
-
```PowerShell
356
-
$nt = Get-AzServiceFabricManagedNodeType -ResourceGroupName TestRG -ClusterName TestClusterName -Name test
357
-
$nt.DataDiskSizeGB = 257
358
-
$nt | Set-AzServiceFabricManagedNodeType
359
-
```
360
-
361
301
## Configure placement properties for a node type
362
302
[Placement properties](service-fabric-cluster-resource-manager-cluster-description.md#node-properties-and-placement-constraints) are used to ensure that certain workloads run only on certain node types in the cluster. Service Fabric managed clusters support configuring these properties via portal, ARM template, or PowerShell.
0 commit comments