Skip to main content

VM Configuration Templates

VM configurations (templates) allow you to define reusable settings for deploying virtual machines. All VM configurations reside in the orka-default namespace and are available to all users and service accounts with access to orka-default. The shorthand alias for vm-config is vmc.

orka vm-config create

Create a VM configuration (template) with the specified settings. The required minimum configuration consists of a base image to use. VM Configuration Name Requirements:
  • Does not exceed 50 characters
  • Consists of lowercase alphanumeric characters or dashes (-)
  • Starts with an alphabetic character and ends with an alphanumeric character
  • Must be unique to the cluster
Syntax:
Options:
Examples:
These options apply only to Intel-based (amd64) VMs on Orka 3.6 and earlier. They were removed in Orka 4.0, which supports Apple silicon only.

orka vm-config list

Show basic or extended information about the available VM configurations. You can list all available configurations or show information about one or more specified VM configurations. Syntax:
Options:
Examples:

orka vm-config delete

Delete the specified VM configurations (templates). Syntax:
Options:
Examples:

Deploying VMs

orka vm deploy

Deploy a VM with the specified configuration. The minimum required configuration consists of an image and a number of CPU cores to assign to the VM. VM Name Behavior:
  • When VM_NAME is not provided: Orka generates a unique name consisting of ‘vm-’ and a unique suffix
  • When VM_NAME is provided: Orka attempts to create the VM using the provided name (must be unique)
  • When both VM_NAME and —generate-name are provided: Orka generates a unique name based on VM_NAME with a unique suffix
VM Name Requirements (when provided):
  • Does not exceed 63 characters (including any generated suffix)
  • Consists of lowercase alphanumeric characters or dashes (-)
  • Starts with an alphabetic character and ends with an alphanumeric character
  • Must be unique to the namespace
Syntax:
Options:
User Data: --userdata requires Orka 4.0 or later and the Orka 4.0 orka-vm-tools in the image. The script runs once per VM, in the background, and doesn’t delay the VM becoming available. Its output goes to /var/log/orka/userdata.log inside the VM, and orka vm list --output wide shows its progress in the USERDATA-PHASE column. For how the script runs, its limits, and an example, see Bootstrap VMs with User Data. Examples - Basic Deployments:
Examples - Targeted Deployments:
Examples - Advanced Deployments:
Examples - VM Configuration Deployments:
These options apply only to Intel-based (amd64) VMs on Orka 3.6 and earlier, and some are mutually exclusive. They were removed in Orka 4.0, which supports Apple silicon only.

Listing VMs

orka vm list

Show basic or extended information about the specified VM(s). The extended table (--output wide) includes the USERDATA-PHASE column for VMs deployed with --userdata: pending, success, failed, skipped, or timeout. The column is empty for VMs without User Data. See Bootstrap VMs with User Data. Syntax:
Options:
Examples:

Deleting VMs

orka vm delete

Delete the specified VMs. This frees up the respective resources and ports on the respective Orka node.
This operation cannot be undone. You will not be able to restore any unsaved or uncommitted data from the VM.
Syntax:
Options:
Examples: