<p>To my understanding <a href="https://kubernetes.io" rel="nofollow noreferrer">Kubernetes</a> is a container orchestration service comparable to <a href="https://aws.amazon.com/ecs/" rel="nofollow noreferrer">AWS ECS</a> or <a href="https://docs.docker.com/engine/swarm/" rel="nofollow noreferrer">Docker Swarm</a>. Yet there are several <a href="https://stackoverflow.com/questions/32047563/kubernetes-vs-cloudfoundry/32238148">high rated questions</a> on stackoverflow that compare it to <a href="https://www.cloudfoundry.org" rel="nofollow noreferrer">CloudFoundry</a> which is a plattform orchestration service. </p>

<p>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. </p>

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

<p>Yes, you can manage VMs with <a href="https://github.com/kubevirt" rel="nofollow noreferrer">KuberVirt</a> as @AbdennourTOUMI pointed out. However, Kubernetes focuses on container orchestration and it also interacts with <a href="https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/" rel="nofollow noreferrer">cloud providers</a> to provision things like Load Balancers that can direct traffic to a cluster.</p>

<p><a href="https://docs.cloudfoundry.org/concepts/overview.html" rel="nofollow noreferrer">Cloud Foundry</a> 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 <a href="https://www.openshift.com/" rel="nofollow noreferrer">OpenShift</a></p>

<p>This is a diagram showing some of the differences:</p>

<p><a href="https://i.stack.imgur.com/pXSXP.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/pXSXP.png" alt="Diagram"></a></p>
