Virtlet: run VMs as Kubernetes pods

The real reason for these projects (Virlet, KubeVirt, RancherVM) is that OpenStack is too damn hard. Even with all this focus on containers these days people still need an onprem VM solution. But the requirements are really pretty simple for most use cases and the cost and complexity of OpenStack is not justified.<p>Edit: disclaimer: my company does RancherVM.

Interesting to see how this <i>really</i> compares to KubeVirt, which seems to be doing the same thing. I don&#x27;t think KubeVirt is &quot;just&quot; pets as far as I understand. [disclaimer: I&#x27;ve been very peripherally involved with KubeVirt because they asked me about integrating virt-v2v support].

I&#x27;m using kubevirt for this. My usecase is to allow preconfigured windows VMs to boot up inside of kubernetes - so that both Windows VMs and Linux containers are manipulated using the same API. It works very well!

What&#x27;s the key difference between Virtlet&#x2F;KubeVirt and just running VMs alongside your Kubernetes pods? Is the main goal to centralize management? That seems reasonable, I&#x27;m just wondering.<p>Also, how does a Kubernetes-managed VM compare to a plain VM from, say, AWS EC2? I imagine it&#x27;s a little less efficient, since the situation I&#x27;m imagining involves various VMs running a Kubernetes pod running the VM, but I may have this all wrong.

reminds me of vmlets term from the virtual virtual machines <a href="https:&#x2F;&#x2F;pages.lip6.fr&#x2F;vvm&#x2F;publications&#x2F;0008SBAC.pdf" rel="nofollow">https:&#x2F;&#x2F;pages.lip6.fr&#x2F;vvm&#x2F;publications&#x2F;0008SBAC.pdf</a>