Actions31
- Backup Actions
- Backup Share Actions
- Catalog Actions
- Cube Actions
- Domain Actions
- Snapshot Actions
- TCP Mapping Actions
- Webhook Actions
Cube → Create
AI-generatedSummary
Create a Krova Cloud Cube in the specified Space by sending its name, OS image, SSH public key, and resource sizes to the Space’s Cubes endpoint. Optionally choose a region or provide a cloud-init script to run on first boot.
Inputs
- Space ID (required) — ID of the Space that will own the Cube.
- Name (required) — Human-readable name for the Cube.
- Image (required) — OS image slug or ID; use Catalog → Get Images to find available values.
- SSH Public Key (required) — Public key written to /root/.ssh/authorized_keys at boot. Supported prefixes include ssh-ed25519, ssh-rsa, ecdsa-sha2-, ssh-dss, and sk-@openssh.com.
- vCPU (required) — Number of virtual CPUs; minimum 1, in whole-number increments. Defaults to 1. The Space’s default cap is 16 and can be raised.
- RAM (GB) (required) — RAM in whole gibibytes; minimum 1, in whole-number increments. Defaults to 1. The Space’s default cap is 32 GB and can be raised.
- Disk (GB) (required) — Disk size in gibibytes; minimum 10, in increments of 5. Defaults to 10. The Space’s default cap is 100 GB and can be raised.
- Region — Region slug from Catalog → Get Regions. Leave empty to let the platform select one.
- User Data — Cloud-init script to run on first boot, up to 16 KB.
Output shape
A single API response item describing the created Cube.
The node sends a POST request to the Space’s /cubes endpoint with the configured values in the JSON body. The response fields depend on the Krova API.