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-maintenance-control.md
+19-3Lines changed: 19 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,8 +11,8 @@ ms.date: 05/07/2024
11
11
---
12
12
13
13
# 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,
16
16
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:
17
17
* Automatic OS Upgrade
18
18
* Automatic extension upgrade
@@ -56,7 +56,7 @@ Download this sample, which contains all the required resources. [Standard SKU S
56
56
57
57
3) Configure maintenance control on the cluster using the following maintenance configuration:
58
58
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)
60
60
61
61
```JSON
62
62
"resources": [
@@ -120,6 +120,22 @@ After the maintenance configuration is created, it has to be attached to the SFM
120
120
}
121
121
```
122
122
123
+
To check the status of the maintenance configuration, use the [Get Maintenance Window action](/rest/api/servicefabric/managedclusters/managed-maintenance-window-status/get).
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).
0 commit comments