Strategies for setting up K8S cluster on Local Machine

Yet another Minikube vs Kind vs K3S comparison

Minikube vs Kind vs K3S

Concepts:

1. Master & Worker Nodes in K8S . refer
2. Single Node Vs Multi Node Cluster.
3. VMs on Hypervisors.
4. Containers.
5. Running Linux VM on Non-linux Host to enable Container Runtime (Docker).
6. K8S Node deployed as a VM. (eg: Minikube)
7. K8S Node deployed as a Container . (eg: Kind — Kubernetes IN Docker)
8. K8S Node deployed as a Process . (eg: K3S)

Kubernetes Nodes

• Multi Node Cluster: K8S cluster with Both Master & Worker Nodes.
• Single Node Cluster: Only Master Node.
• Hypervisor : A piece of code to emulate hardware and make VMs possible.(Hardware Virtualisation)
• Containers: OS Virtualisation
• Running Linux VM in Non-Linux Host:
  i.e., Docker Engine runs within a linux VM on top of a Hypervisor
• K8S Node as a VM:
  Both Master and Worker nodes are spawned as VMs made out of pre-baked VM images.

• K8S Node as a Process:
  Have essential Kubernetes components packaged into a single executable.
  i.e., Master process and Worker process. Lightweight!!!

K3S architecture : K3S Server Process + K3S Agent Process Interacting with Container Runtime

• K8S Node as a Container: (Docker in Docker)
  Deploying Kubernetes nodes as a container, which implicates a container runtime running inside the node container.

Summary:

Minikube vs Kind vs K3S

https://www.jambit.com/en/latest-info/toilet-papers/minikube-vs-kind-vs-k3s-which-local-kubernetes-cluster-should-i-use/

References:

MiniKube, Kubeadm, Kind, K3S: how to start with Kubernetes?

Colima — Docker & K8S for local development