Hacker News Reader

Comment by rwmj | Hacker News Reader

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

View on HN

You can't have a StatefulSet of VMs on KubeVirt, although you may want one if you're using unikernels or want to run a nested Kubernetes cluster for testing, like here: https://github.com/Mirantis/virtlet/blob/master/examples/k8s... On the other hand, you can't have VM migrations with Virtlet.

Yes, right now we were more focusing on the 1:1 case. Our OfflineVirtualMachine is basically a StatefulSet with replica 1. For stateless scaling we have a VirtualMachineReplicaSet. A StatefulVirtualMachineSet will probably be added soon to KubeVirt.

Be nice if there was just one "virt for Kube" technology. I guess virt-v2v will end up having to support both.

Given that the container ecosystem is a huge land rush with many obviously missing pieces, there are going to be multiple projects for every piece.

It seems that KubeVirt is implemented as an operator and registers new resource types, which is an approach I like.

I'd have for someone to do a kubectl delete pod --all thinking they are only deleting stateless apps and getting rid of VMs too.

As an aside - I saw you a few years ago in Gloucester UK and you taught me loads about virtualisation. Thank you Richard.

Reply on news.ycombinator.com