Kalisto/ documentation source (permission required) ↗
On this page

#Optional Lima backend

Native Lima vz is an explicit macOS alternative, including Intel Macs and macOS versions older than 26. Rosetta is opt-in. The default Apple-container path never silently falls back to Lima, never discovers a Lima template, and does not prepare Lima disk assets.

#Prepare and start explicitly

kalisto pull --backend lima --addons cni/cilium
kalisto up --backend lima --workers 2 --addons cni/cilium

Or persist the choice in kalisto.toml:

[cluster]
backend = "lima"

Preparation manages Lima and a sanitized compressed Ubuntu/k3s raw disk through native VZ without starting Kubernetes. It also prepares the selected boot images and managed tools. No hand-built qcow2, manual template, host Helm/Crane or QEMU installation is needed for this installed product flow. The optional legacy maintainer finalize script does require QEMU; it is a separate workflow, not an installation prerequisite.

Select Cilium explicitly in both commands for pod networking. Prepared profiles support no CNI or Cilium and optional lb/servicelb only; install other add-ons after startup. See preparation for offline boot and per-cluster Cilium TLS handling.

#Persisted identity and storage

Existing clusters retain their recorded backend. Selecting another engine does not convert their disks. down stops VMs and retains disks/state; up resumes. destroy permanently deletes the named cluster while prepared assets remain cached. Always inspect and obtain authorization before deleting existing state.

Cold archives currently require macOS native VZ, compatible CPU architecture and the pinned Lima version. They cannot be restored as Apple-container or Firecracker clusters; native restore evidence is still pending.

#Performance and maintainer tooling

The optional release benchmark passed four runs at 56.07s, 53.84s, 54.26s and 54.83s on the development Mac. It used the actual installed binary from an empty directory with system-only PATH, three fresh VMs, authenticated API, all Cilium rollouts, and both-worker DNS/cross-node Service HTTP. VM creation/image imports are timed; pull is not. These are not Apple-container measurements or universal hardware guarantees.

The release budget test supplies its own empty workdir and does not use KALISTO_LIMA_TEMPLATE. See performance and opt-in live tests. Contributor tooling separately documents legacy image build/publication, XDG artifact installation, and Lima substrate/k3s probes. The probes' default Flannel baseline must not be confused with prepared product startup's no-CNI default.