Blog

A VirtualMachine is a Kubernetes object. You write it as YAML, apply it with kubectl apply -f, and it shows up under kubectl get vm like any other resource — namespaced, RBAC-able, watchable, governed by labels. This tutorial turns that idea into a running Linux VM in about fifteen minutes. Why a …

The Kubermatic Virtualization Dashboard is the per-cluster operator UI introduced in v1.1.0. It gives you a VM-aware browser — start/stop/console controls, Nodes view, Data Volumes, Firewalls, Load Balancers — for the cluster it lives in. It is shipped and reconciled by the kubev installer itself, …

A KubeVirt VM has four lifecycle verbs: start, stop, pause, and unpause. Stop deletes the VirtualMachineInstance and its virt-launcher pod — memory and CPU are released. Pause freezes the guest at the hypervisor level but keeps the pod and memory in place. Stop is cheap; pause is instant. You drive …

Day-two networking questions for a KubeVirt VM all reduce to the same insight: a running VM is wrapped inside a pod. The networking primitives Kubernetes already gives you for pods — labels, Services, NetworkPolicies — apply directly. There’s almost nothing VM-specific to learn. Almost. …

Every VM you’ve booted so far has been ephemeral. The container disk image is read-only, runtime writes are held in memory, and everything you change disappears when the VMI restarts. That’s the right default for learning, and the wrong default for anything you want to keep. This …

Introduction You have a Kubernetes cluster running your containerized workloads. Now you want to add virtual machines to the mix — maybe you have legacy applications that need a full OS, or you are evaluating a migration path away from VMware. Either way, you need KubeVirt installed and working. In …

Broadcom’s acquisition of VMware changed the economics of enterprise virtualization overnight. License costs doubled or tripled for many organizations, and the perpetual license model that teams relied on for budget predictability is gone. If you are reading this, you are probably feeling that …

KubeVirt adds a virtualization layer on top of Kubernetes, which means debugging spans two stacks: the Kubernetes layer (pods, services, PVs) and the KVM/libvirt layer (QEMU processes, virtio drivers, disk images). When something breaks, you need to know which stack to look at first and how to trace …

Introduction Most organizations are not 100% containerized, and they probably never will be. You have legacy applications that assume a full operating system. You have Windows workloads that cannot run in a container. You have specialized software — think telecom network functions, database …