Juno Orion Virtual Machines via KubeVirt¶
Managing your on-prem virtual machines has never been easier with Orion and KubeVirt. Create vm workloads, golden images, and migrate your vm's with ease.
What is KubeVirt?¶
KubeVirt extends Kubernetes to run traditional virtual machines alongside containers. This enables you to:
- Run Windows workloads on your Kubernetes infrastructure (Windows 10, Windows 11, Windows Server)
- Consolidate infrastructure by managing VMs and containers through a single platform
- Leverage Orion's orchestration for VM lifecycle management, resource allocation, and golden image deployment
- Enable VDI workflows with built-in connection broker capabilities through dynamic port assignment
With Orion + KubeVirt, you can run Adobe Creative Suite, Autodesk products, Houdini, DaVinci Resolve, and other Windows-only applications within your Kubernetes cluster—all managed through the familiar Orion interface.
Coming from other Platforms?¶
Coming from Proxmox, VMware, or Similar Platforms? If you're familiar with traditional hypervisors, here's how Orion + KubeVirt maps to concepts you already know:
| Traditional VM Concept | Orion Equivalent |
|---|---|
| VM Template | Workload Template (Genesis → Workloads) |
| ISO Library | HTTP mounts with direct URLs (or self-hosted ISOs over HTTP) |
| Datastore / Storage | DataVolumes and PVCs (managed automatically) |
| Clone / Linked Clone | Golden Image → Clone mount type |
| vCPU / Memory allocation | CPU/Memory requests and limits in template |
| Port forwarding / NAT | Port configuration in template |
| Console / VNC | Connect button → URL/Name option |
| VM Snapshot | Clone action on DataVolumes |
Key Differences to Keep in Mind:
- No GUI for all settings. Some configurations that are point-and-click in Proxmox are handled through template definitions in Orion. The tradeoff is repeatability — once your template is right, every deployment is identical.
- VNC is barebones. You're used to a decent console experience in Proxmox/VMware. Here, the VNC viewer is intentionally minimal — it's for setup and emergencies, not daily use. Plan on RustDesk or similar for actual work.
- Resource limits are strict. No "unlimited" or "ballooning" — you define what the VM gets, and that's what it gets. Please plan accordingly. This feature is being explored.
- Kubernetes-native networking. Instead of virtual switches and bridges, you're working with Ports and Kubernetes services. The Connect button abstracts most of this for you.
What You'll Find Familiar:
- VirtIO drivers — same process as Proxmox
- Golden image workflow — conceptually identical to template creation
- ISO booting and installation — same BIOS/UEFI experience
- Windows quirks — still the same Windows quirks
The mental shift is thinking of VMs as "workloads" managed through templates rather than individual machines you configure one at a time. Once that clicks, you'll find the workflow surprisingly efficient for deploying at scale.