Blog

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. …

Introduction The Kubernetes Ingress API served the community well for years, but its limitations are well documented. There is no support for traffic splitting, header-based routing, or TCP/UDP routing. Everything gets crammed into annotations that differ between controllers. If you have ever tried …

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 …