This is the fourth weekly update from the KubeVirt team.

We are currently driven by

• Being easier to be used on Kubernetes and OpenShift

• Enabling people to contribute

• Node Isolator use-case (more informations soon)

This week you can find us at:

• Ohio Linux Fest (@stu-gott) “KubeVirt, Virtual Machine Management Using Kubernetes” https://ohiolinux.org

This week we achieved to:

• ReplicaSet for VirtualMachines (@rmohr) (https://github.com/kubevirt/kubevirt/pull/453)

• Swagger documentation improvements (@rmohr, @lukas-bednar) (https://github.com/kubevirt/kubevirt/pull/475)

• Hot-standby for our controller (@cynepco3hahue) (https://github.com/kubevirt/kubevirt/pull/461)

• domxml/VM Spec mapping rules proposal (@rmohr, @michalskrivanek) (https://github.com/kubevirt/kubevirt/pull/466)

• Launch flow improvement proposal (@davidvossel) (https://github.com/kubevirt/kubevirt/pull/469)

In addition to this, we are also working on:

• Debug layer 3 network connectivity issues for VMs (@vladikr) (https://github.com/kubevirt/kubevirt/pull/450)

• Review of the draft code for the api server aggregation (@stu-gott) (https://github.com/kubevirt/kubevirt/pull/355)

Take a look at the pulse, to get an overview over all changes of this week: https://github.com/kubevirt/kubevirt/pulse

Finally you can view our open issues at https://github.com/kubevirt/kubevirt/issues

And keep track of events at our calendar 18pc0jur01k8f2cccvn5j04j1g@group.calendar.google.com

If you need some help or want to chat you can find us on <irc://irc.freenode.net/#kubevirt>