Reading notes from 2022; revised November 17, 2026. Reported architecture and scale refer to the source period.

Distributions and launchers differ

A lightweight Kubernetes distribution supplies a cluster implementation. A tool that launches cluster nodes inside containers solves a different packaging problem. Separating those roles makes comparisons more useful.

Option Role in a local exercise
k0s Kubernetes distribution
MicroK8s Packaged Kubernetes distribution
kind Kubernetes nodes in containers, useful for repeatable tests
k3s Lightweight Kubernetes distribution
k3d Runs k3s nodes in containers
Minikube Local cluster tool with selectable drivers

This is a conceptual taxonomy, not a current OS/support matrix. Check the chosen release for supported hosts, runtime, networking, and minimum resources.

Runtime terminology matters

Containerd and CRI-O are container runtimes, not interchangeable names for the same containers. A cluster distribution’s packaged defaults can change. Read its runtime documentation rather than assuming that one runtime manages another runtime’s containers.

Compare on the same workload

For a proposed CI exercise, create a cluster, load one test image, deploy a service, wait for readiness, run a request, and delete the cluster. Measure creation time, resource use, cleanup reliability, and failure diagnostics.

Include architecture compatibility: an ARM developer laptop and an x86 runner may need different images. A successful application test does not demonstrate production storage or network equivalence.

Record the cluster-tool version, Kubernetes version, container runtime, host OS, and test image digest with results. The original 2022 links are historical context; do not copy their resource estimates into a current capacity plan.

References