K
Q

Does Kubernetes support VM / node provisioning & management?

10/19/2018

To my understanding Kubernetes is a container orchestration service comparable to AWS ECS or Docker Swarm. Yet there are several high rated questions on stackoverflow that compare it to CloudFoundry which is a plattform orchestration service.

This means that CloudFoundry can take care of the VM layer, updating and provisioning VMs while moving containers avoiding downtime. Therefore the comparison to Kubernetes makes limited sense to my understanding.

Am I misunderstanding something, does Kubernetes support provisioning and managing the VM layer too?

-- B M
cloudfoundry
kubernetes
paas

Similar Questions

Does CloudFoundry support multiple containers per app?
Liveness probe failed: Get http://192.168.9.69:8080/health: read tcp 10.9.44.118:44143->192.168.9.69:8080: read: connection reset by peer
Using NGINX on-prem as LB for kubernetes
Deleted Kubernetes Deployment but Node(docker) containers keep recreating themselves

2 Answers

10/19/2018

Yes, you can manage VMs with KuberVirt as @AbdennourTOUMI pointed out. However, Kubernetes focuses on container orchestration and it also interacts with cloud providers to provision things like Load Balancers that can direct traffic to a cluster.

Cloud Foundry is a PaaS that provides much more than Kubernetes at the lower level. Kubernetes can run on top of an IaaS like AWS together with something like OpenShift

This is a diagram showing some of the differences:

Diagram

-- Rico
Source: StackOverflow
10/20/2018

As for VM, my answer is YES; you can run VM as workload in k8s cluster.

Indeed, Redhat team figured out how to run VM in the kubernetes cluster by adding the patch KubeVirt.

example from the link above.

apiVersion: kubevirt.io/v1alpha2
kind: VirtualMachine
metadata:
  creationTimestamp: null
  labels:
    kubevirt.io/vm: vm-cirros
  name: vm-cirros
spec:
  running: false
  template:
    metadata:
      creationTimestamp: null
      labels:
        kubevirt.io/vm: vm-cirros
    spec:
      domain:
        devices:
          disks:
          - disk:
              bus: virtio
            name: registrydisk
            volumeName: registryvolume
          - disk:
              bus: virtio
            name: cloudinitdisk
            volumeName: cloudinitvolume
        machine:
          type: ""
        resources:
          requests:
            memory: 64M
      terminationGracePeriodSeconds: 0
      volumes:
      - name: registryvolume
        registryDisk:
          image: kubevirt/cirros-registry-disk-demo:latest
      - cloudInitNoCloud:
          userDataBase64: IyEvYmluL3NoCgplY2hvICdwcmludGVkIGZyb20gY2xvdWQtaW5pdCB1c2VyZGF0YScK
        name: cloudinitvolume

Then:

kubectl create -f vm.yaml
virtualmachine "vm-cirros" created
-- Abdennour TOUMI
Source: StackOverflow