Policy templates
Last updated
On Team, policy templates save a scaling policy once for the organisation, and a member copies it into node groups on purpose. A new version reaches no group by itself.
What is a template?
A scaling policy saved once for the organisation: a preset, custom rules or a target to track, with the cooldown, the warm-up, the rate cap and the cost guard. Nothing else: min, max, the stock fallback and the advanced settings stay each group’s own. An organisation keeps up to 50, each with a name and an optional description, on Autoscaling → Policy templates.
How do versions work?
A changed policy saves the next version. A new name or description does not.
How does a group take a template?
- At Go Live, choosing the template beside the presets.
- In the group’s Settings, choosing it the same way.
- On the template’s page, with Apply to groups, ticking the groups.
Each group copies the version at that moment and records it, and the change is on its timeline.
Does a group follow a template’s changes?
No: a new version changes no group. The template’s page shows how many groups run each version, and a group’s Settings says when a newer version exists and takes it only with Apply version N.
How does a group leave a template?
Changing a group’s policy by hand, in its Settings or through the API, keeps the policy and drops the template. Deleting a template keeps every group’s policy, without the template.
Who can use templates?
The owner and the admins create, change, apply and delete templates; every member sees them. Templates come with Team. On another plan they stay readable and are not created, changed or applied. Creating, changing and deleting a template are in the audit log.
Are templates in the API?
Not yet: the group API shows a group’s policy, not its template.