Provisioning Policy Settings
< scope | provisioning policy create workflow
Overview
Set region limits, cluster restrictions, cost controls, and instance type allowances to manage where and how clusters are provisioned. This will help you optimise resource usage, manage costs, and enforce consistent standards across workspaces.
📚 For more details on key points, refer to the overview section.
📚 Explore the properties section for additional information on each UI property.
CLI Instructions
Follow the instructions in the details section.
Web Interface Instructions
Steps
- Fill in the policy details as outlined in the properties section.
- Click Continue to proceed
Screenshot(s)
Properties
| Field | Description |
|---|---|
| Region | Optional. Limits where clusters can be provisioned. |
| Maximum number of clusters per workspace | Optional. Maximum number of clusters that can be provisioned in a workpace. |
| Maximum costs of clusters per workspace | Optional. The maximum estimated monthly cost allowed for each cluster. This includes the estimated costs for the initial node pool configuration as well as any potential scaling, ensuring the total estimated cost remains within limits. Note this estimates the cluster cost using the cloud provider's public pricing information, so it will not take into account any commited-use or other discounts you may have. |
| Maximum nodes per cluster | Optional. The maximum number of nodes permitted across all node pools of a cluster. |
| Restrict instance types | Turn the toggle on if you want to restrict the machine/instance types. |
| - Allowed instance types | The machine/instance types that users can choose from for their clusters. You can optionally limit the maximum number of an instance type permitted as well, for example, to limit the permitted usage of an expensive instance type. |