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: docs/admin/templates/extending-templates/prebuilt-workspaces.md
+7-1Lines changed: 7 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -235,12 +235,18 @@ The system always maintains the desired number of prebuilt workspaces for the ac
235
235
236
236
### Managing resource quotas
237
237
238
-
Prebuilt workspaces can be used in conjunction with [resource quotas](../../users/quotas.md).
238
+
To help prevent unexpected infrastructure costs, prebuilt workspaces can be used in conjunction with [resource quotas](../../users/quotas.md).
239
239
Because unclaimed prebuilt workspaces are owned by the `prebuilds` user, you can:
240
240
241
241
1. Configure quotas for any group that includes this user.
242
242
1. Set appropriate limits to balance prebuilt workspace availability with resource constraints.
243
243
244
+
When prebuilt workspaces are configured for an organization, Coder creates a "prebuilds" group in that organization and adds the prebuilds user to it. This group has a default quota allowance of 0, which you should adjust based on your needs:
245
+
246
+
-**Set a quota allowance** on the "prebuilds" group to control how many prebuilt workspaces can be provisioned
247
+
-**Monitor usage** to ensure the quota is appropriate for your desired number of prebuilt instances
248
+
-**Adjust as needed** based on your template costs and desired prebuilt workspace pool size
249
+
244
250
If a quota is exceeded, the prebuilt workspace will fail provisioning the same way other workspaces do.
0 commit comments