first party plugins
These executables live under cmd/corral-* and speak the
corral.plugin/v1 metadata handshake. tuna-os publishes them through the
curated marketplace.
| Plugin | Purpose | Supported backends | Main capabilities |
|---|---|---|---|
aws-power | Power EC2 VM hosts on and off (host-power hook) | all | Tag-discovered EC2 instances, start/stop |
auth | Optional reverse-proxy authentication | all (web transport) | OIDC SSO, htpasswd Basic Auth, passkeys, peer service tokens |
backup | VM disk backup and restore | KubeVirt | KubeVirt export, rclone/S3/R2, schedules |
bootc | Bootable-container VM workflow | KubeVirt | On-cluster disk builds and rebuilds |
gpu | GPU/PCI passthrough | KubeVirt | Device discovery, permitted devices and attachment |
proxmox | Proxmox VE compatibility service | KubeVirt | /api2/json HTTP API backed by KubeVirt |
schedule | Lifecycle windows | KubeVirt | Kubernetes CronJobs for VM start/stop |
snapsched | Snapshot retention schedules | KubeVirt | KubeVirt snapshots and pruning CronJobs |
windows | Windows VM creation | KubeVirt | UEFI, TPM, Hyper-V, installer and virtio media |
vdi | Desktop pools | KubeVirt | Static and ephemeral VM pools from golden VM clones, Lease claims, CT-backed ephemeral pools, one-click connect |
corral-vdi provides static desktop pools for Phase 1 and CT-backed ephemeral
pools. The self-service broker of Phase 2 is part of corral web
(ADR-0013). On KubeVirt, the broker on
persistent VM pools is Stable. The corral vdi CLI, ephemeral and CT-backed
pools, USB redirection and device checks are Preview.
docs/vdi.md gives the evidence for each level. RFC-0001 governs these plugins. docs/vdi.md and docs/vdi-ct-pools.md document them. docs/vdi-epic-status.md tracks the dependency gates of the epic.
corral-incus is a compatibility
binary for older installations. Incus is now a built-in backend, and tuna-os does
not publish it as a marketplace plugin.
Marketplace v2 needs immutable URLs and SHA-256 checksums. Corral also verifies the Sigstore signature and the signed SPDX SBOM of each first-party plugin against an identity in its code (plugin-marketplace.md). It shows permissions and records the installed provenance.
The matrix is deliberately honest: core inventory and lifecycle support for a backend does not imply that every workflow plugin supports it. The extension issues #129 through #134 track adapter work. Until those land, the marketplace and web UI expose the limitation before install.