Skip to content

Commit 60171dc

Browse files
authored
Merge pull request #2680 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-compute-docs (branch main)
2 parents c46019d + 69427fc commit 60171dc

File tree

1 file changed

+19
-3
lines changed

1 file changed

+19
-3
lines changed

articles/service-fabric/how-to-managed-cluster-maintenance-control.md

Lines changed: 19 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,8 @@ ms.date: 05/07/2024
1111
---
1212

1313
# Introduction to MaintenanceControl on Service Fabric managed clusters
14-
Service Fabric managed clusters have multiple background operations that are necessary to the keep all the cluster updated, thus ensuring security and reliability. Even though these operations are critical, but executing in the background can result in the service replica to move to a different node. This failover results in
15-
undesired and unnecessary interruptions, if the maintenance operation executes during the peak business hours. With the support for MaintenanceControl in Service Fabric managed clusters, customers would be able to define a recurring (daily, weekly, monthly) and custom maintenance window for their SFMC cluster resource,
14+
Service Fabric managed clusters have multiple background operations that are necessary to keep the entire cluster updated, thus ensuring security and reliability. Even though these operations are critical, executing them in the background can result in the service replica moving to a different node. This failover results in
15+
undesired and unnecessary interruptions, if the maintenance operation executes during the peak business hours. With the support for MaintenanceControl in Service Fabric managed clusters, customers can define a recurring (daily, weekly, monthly) and custom maintenance window for their SFMC cluster resource,
1616
as per their needs. All background maintenance operations will be allowed to execute only during this maintenance window. MaintenanceControl is applicable to these background operations:
1717
* Automatic OS Upgrade
1818
* Automatic extension upgrade
@@ -56,7 +56,7 @@ Download this sample, which contains all the required resources. [Standard SKU S
5656

5757
3) Configure maintenance control on the cluster using the following maintenance configuration:
5858

59-
This maintenance configuration defines a schedule for updates to happen everyday from 10PM PST for 5hours, starting 30-05-2023. [More details about maintenance configuration](/azure/templates/microsoft.maintenance/maintenanceconfigurations)
59+
This maintenance configuration defines a schedule for updates to happen every day from 10PM PST for 5 hours, starting 30-05-2023. [More details about maintenance configuration](/azure/templates/microsoft.maintenance/maintenanceconfigurations)
6060

6161
```JSON
6262
"resources": [
@@ -120,6 +120,22 @@ After the maintenance configuration is created, it has to be attached to the SFM
120120
}
121121
```
122122

123+
To check the status of the maintenance configuration, use the [Get Maintenance Window action](/rest/api/servicefabric/managedclusters/managed-maintenance-window-status/get).
124+
125+
```powershell
126+
$resourceGroupName = "testResourceGroup"
127+
$clusterName = "testCluster"
128+
Invoke-AzResourceAction -ResourceGroupName $resourceGroupName -ResourceName $clusterName -ResourceType Microsoft.ServiceFabric/managedclusters -Action getMaintenanceWindowStatus
129+
```
130+
131+
If there are missing notifications and there is a time critical pending update that can be safely applied, a 5 hour maintenance window can be manually applied using the [Apply Maintenance Window Status action](/rest/api/servicefabric/managedclusters/managed-apply-maintenance-window/post).
132+
133+
```powershell
134+
$resourceGroupName = "testResourceGroup"
135+
$clusterName = "testCluster"
136+
Invoke-AzResourceAction -ResourceGroupName $resourceGroupName -ResourceName $clusterName -ResourceType Microsoft.ServiceFabric/managedclusters -Action applyMaintenanceWindow
137+
```
138+
123139
>[!NOTE]
124140
>* To disable the maintenance control on the cluster, unassign/delete the assignment for the cluster.
125141
>* The maintenance resources and the SFMC cluster resource should be created in the same **Azure Region** and **Subscription**.

0 commit comments

Comments
 (0)