Kvindo™ Cloud Docs
A VM On/Off Schedule powers a VM on or off on a recurring schedule — for example, stopping development VMs every evening and starting them each morning to save costs. It is a standalone resource: attach it to one or more VMs via the VM's onOffScheduleIds.
• Schedule — a cron expression (e.g. 0 20 * * * = daily at 20:00) plus its format
• Target state — what happens when the schedule fires: running powers the VM on, stopped powers it off. Use two schedules (one running, one stopped) for a working-hours window
• Attachment — reference it from one or more VMs' onOffScheduleIds; the schedule itself has no target VM field
• Enabled — toggle the schedule on or off without deleting it
| UI Name | API / kc name | Terraform name | Optional | Format | Default | Is read only | Description |
|---|---|---|---|---|---|---|---|
| Enabled | spec.enabled |
spec.enabled |
No | boolean (nullable) | — | No | Whether the schedule is active |
| Schedule Format | spec.scheduleFormat |
spec.schedule_format |
No | string (nullable) | cron |
No | Format of the schedule expression. Only cron is currently accepted |
| Schedule | spec.schedule |
spec.schedule |
No | string (nullable) | — | No | The schedule expression, e.g. cron 0 20 * * * |
| Target state | spec.targetState |
spec.target_state |
No | string — running/stopped |
— | No | Power the VM on or off when the schedule fires |
| Runs | status.runs |
status.runs |
— | array of objects | — | Yes | The last 10 runs of this schedule, newest first |
An evening auto-stop schedule; attach it to a VM via onOffScheduleIds (on_off_schedule_ids in Terraform).
Terraform
Python SDK
kc CLI
Resource docs
More in this section
Reference