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/aks/planned-maintenance.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,11 +11,11 @@ author: qpetraroia
11
11
12
12
# Use Planned Maintenance to schedule and control upgrades for your Azure Kubernetes Service (AKS) cluster (preview)
13
13
14
-
Your AKS cluster has regular maintenance performed on it automatically. By default, this work can happen at any time. Planned Maintenance allows you to schedule weekly maintenance windows to perform updates and minimize workload impact. Once scheduled, maintenance will occur only during the window you selected.
14
+
Your AKS cluster has regular maintenance performed on it automatically. By default, this work can happen at any time. Planned Maintenance allows you to schedule weekly maintenance windows to perform updates and minimize workload impact. Once scheduled, upgrades occur only during the window you selected.
15
15
16
16
There are currently two available configuration types: `default` and `aksManagedAutoUpgradeSchedule`:
17
17
18
-
-`default` corresponds to a basic configuration that will update your control plane and your kube-system pods on a virtual machine scale sets instance. It is a legacy configuration that is mostly suitable for basic scheduling of [weekly releases][release-tracker]. Another way of accomplishing this using pre-configured windows is detailed at [use Planned Maintenance to schedule weekly releases][pm-weekly]
18
+
-`default` corresponds to a basic configuration that updates your control plane and your kube-system pods on a virtual machine scale sets instance. It is a legacy configuration that is mostly suitable for basic scheduling of [weekly releases][release-tracker]. Another way of accomplishing this behavior, using pre-configured windows, is detailed at [use Planned Maintenance to schedule weekly releases][pm-weekly]
19
19
20
20
-`aksManagedAutoUpgradeSchedule` is a more complex configuration that controls when upgrades scheduled by your designated auto-upgrade channel are performed. More finely controlled cadence and recurrence settings are possible. For more information on cluster auto-upgrade, see [Automatically an Azure Kubernetes Service (AKS) cluster][aks-upgrade].
21
21
@@ -70,7 +70,7 @@ An `aksManagedAutoUpgradeSchedule` has the following properties:
70
70
|Name|Description|Default value|
71
71
|--|--|--|
72
72
|`utcOffset`|Used to determine the timezone for cluster maintenance|`+00:00`|
73
-
|`startDate`|The date on which the maintenance window will begin to take effect|The current date at creation time|
73
+
|`startDate`|The date on which the maintenance window begins to take effect|The current date at creation time|
74
74
|`startTime`|The time for maintenance to begin, based on the timezone determined by `utcOffset`|N/A|
75
75
|`schedule`|Used to determine frequency. Three types are available: `Weekly`, `AbsoluteMonthly`, and `RelativeMonthly`|N/A|
76
76
|`intervalWeeks`|The interval in weeks for maintenance runs|N/A|
0 commit comments