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: src/current/cockroachcloud/advanced-cluster-management.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -142,17 +142,19 @@ Setting maintenance windows requires the [Cluster Admin]({% link cockroachcloud/
142
142
Maintenance operations that are critical for cluster security or stability may be applied outside of the maintenance window, and upgrades that begin in a maintenance window may not always be completed by the end of the window.
143
143
{{site.data.alerts.end}}
144
144
145
-
To set a maintenance window:
145
+
To set a maintenance window in the {{ site.data.products.cloud }} console:
146
146
147
147
1. Click the pencil icon next to **Cluster maintenance** to edit the maintenance window.
148
148
1. From the **Day** dropdown, select the day of the week during which maintenance may be applied.
149
149
1. From the **Start of window** dropdown, select a start time for your maintenance window in UTC.
150
150
151
151
The window will last for 6 hours from the start time.
152
152
153
-
1. (Optional) If you want to delay automatic patch upgrades for 60 days, switch **Delay patch upgrades** to **On**.
153
+
1. (Optional) If you want to delay automatic patch upgrades, switch **Delay patch upgrades** to **On**. You can set a deferral period of 30, 60, or 90 days after the patch is released.
154
154
155
-
Enable this setting for production clusters to ensure that development and testing clusters are upgraded before production clusters. This setting applies only to patch versions and not to other kinds of upgrades.
155
+
Enable this setting for production clusters to ensure that development and testing clusters are upgraded before production clusters. This setting applies only to patch versions and not to other kinds of upgrades. The patch upgrade occurs during a maintenance window after the deferral period.
156
+
157
+
You can also configure maintenance windows and patch upgrade deferral periods using the {{ site.data.products.cloud }} API.
Copy file name to clipboardExpand all lines: src/current/cockroachcloud/cloud-api.md
+92Lines changed: 92 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1021,3 +1021,95 @@ If the request is successful, the client receives a response with the name of th
1021
1021
~~~
1022
1022
1023
1023
Where `<sql_username>` is the name of the SQL user whose password was changed.
1024
+
1025
+
## Configure a CockroachDB Advanced cluster's maintenance window
1026
+
1027
+
To configure a [maintenance window]({% link cockroachcloud/advanced-cluster-management.md %}#set-a-maintenance-window) on a CockroachDB {{ site.data.products.advanced }} cluster, send a `PUT` request to the `/v1/clusters/{cluster_id}/maintenance-window` endpoint.
1028
+
1029
+
{{site.data.alerts.callout_success}}
1030
+
The service account associated with the secret key must have the Cluster Admin or Cluster Operator [role]({% link cockroachcloud/authorization.md %}#organization-user-roles).
The cluster ID used in the Cloud API is different from the routing ID used when [connecting to clusters]({% link cockroachcloud/connect-to-your-cluster.md %}).
1046
+
{{site.data.alerts.end}}
1047
+
-`{offset_duration}` is the start of the maintenance window, calculated as the amount of time after the start of a week (Monday 00:00 UTC) to begin the window.
1048
+
-`{window_duration}` is the length of the maintenance window, which must be greater than 6 hours and less than one week.
1049
+
1050
+
A cluster's existing maintenance window can be viewed with a `GET` request to the `/api/v1/clusters/{cluster_id}/maintenance-window` endpoint:
Automatic patch upgrades can be delayed for a period of 30, 60, or 90 days to ensure that development and testing clusters are upgraded before production clusters. This setting applies only to patch versions and not to other kinds of upgrades.
1085
+
1086
+
To set a patch upgrade deferral policy, send a `PUT` request to the `/api/v1/clusters/{cluster_id}/version-deferral` endpoint.
1087
+
1088
+
{{site.data.alerts.callout_success}}
1089
+
The service account associated with the secret key must have the Cluster Admin or Cluster Operator [role]({% link cockroachcloud/authorization.md %}#organization-user-roles).
The cluster ID used in the Cloud API is different from the routing ID used when [connecting to clusters]({% link cockroachcloud/connect-to-your-cluster.md %}).
1105
+
{{site.data.alerts.end}}
1106
+
-`{deferral_policy} is the length of the deferral window, set to `"DEFERRAL_30_DAYS"`, `"DEFERRAL_60_DAYS"`, or `"DEFERRAL_90_DAYS"`. Set to `"FIXED_DEFERRAL"` to defer upgrades by 60 days, or `"NOT_DEFERRED"` to remove the deferral policy and apply automatic patch upgrades immediately.
1107
+
1108
+
To view the existing patch deferral policy and current patch upgrade deferrals, send a `GET` request to the `/api/v1/clusters/{cluster_id}/version-deferral` endpoint.
0 commit comments