The Horrors of Upgrading Etcd Beneath Kubernetes

Re:The Horrors of Upgrading Etcd Beneath Kubernetes by outworlder on Friday July 06, 2018 @09:18PM (#17476301)

Indeed.

But I think that doesn't go far enough: I want to provide K8s with a YAML file and have Kubernetes itself go and create and provision a VM for me. I.e, I want to "kill" Terraform. I don't care about a 'fabric' network (although that could be convenient), just give me an IP that I can reach even it if is external to the cluster. VMs could be just one more resource that can be created or destroyed by k8s, just like network-based storage today.

I haven't found this exact use-case implemented yet. If noone else builds it in the coming months I'll probably start doing it.

[ Parent | on HN ]

Re:The Horrors of Upgrading Etcd Beneath Kubernetes by smarterclayton on Friday July 06, 2018 @11:55PM (#17476890)

We did something simple for GCP and CI jobs, when we needed to have VMs in a certain project to launch Kubernetes single node testing - https://github.com/openshift/ci-vm-operator/

The base pattern should be pretty easy to modify, although the use case here is very specific.

[ Parent | on HN ]

Re:The Horrors of Upgrading Etcd Beneath Kubernetes by hunter_n on Saturday July 07, 2018 @01:41AM (#17477240)

Have you looked at Virtlet or Kubevirt?

[ Parent | on HN ]