Virtualization

Where Kubernetes fits in the stack

Compare Kubernetes worker nodes backed by VMs with worker nodes running on physical servers.

VM-backed worker nodevirtual-hardware ↔ virtual-hypervisorvirtual-hypervisor ↔ virtual-workervirtual-worker ↔ virtual-runtimevirtual-runtime ↔ virtual-pod-avirtual-runtime ↔ virtual-pod-bSchedules workloadsSchedules workloadsvirtual-service ↔ virtual-pod-avirtual-service ↔ virtual-pod-bPhysical hostPhysical hostHypervisorHypervisorWorker node VMWorker node VMContainer runtimeContainer runtimePod APod APod BPod BKubernetes control planeKubernetes control planeServiceService
Legend

Current step

The hypervisor provides worker VMs

Physical hosts and a hypervisor sit below the Kubernetes worker node.

Kubernetes schedules and reconciles container workloads; it is not the hypervisor. A worker node may be a VM or a physical server, and the control plane manages workloads across nodes.

Documentation example: addresses use the RFC 5737 ranges and ASNs use the reserved private range. Nothing here connects to a real network.

Tags

  • virtualization
  • kubernetes
  • container
  • node
  • hypervisor
  • layers

Lessons using this diagram