Minikube & Three Different Local Kubernetes Learning Environments
summary
Minikube runs local Kubernetes via three concrete environments—hypervisor VMs (VirtualBox/Hyper‑V), a low‑overhead docker driver system container, and a non‑driver bare‑metal mode—and uses kubeadm plus preloaded tarballs to bootstrap clusters. Multi‑node becomes production‑grade (multi-node GA Dec 2020), start times improve dramatically (86% faster start time with ~20% less CPU), current start ≈18s with a <15s goal, supports amd64/arm64, containerd/cri‑o/podman, image load/build commands, 28 add‑ons, and removes the old docker shim. Choose VM for isolation and compatibility, docker driver for speed, non‑driver for minimal overhead.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:39install kubernetes applications
- 5:54install additional add-ons to the cluster
- 15:57install a server running linux
- 16:26install the kubernetes control plate components in mini cube
- 23:38preload all the needed containers from a tarball into the environment
- 26:31using the standard cube adm installer
- 31:01running kubernetes in docker
related talks
47mMinikube
29mMinikube Intro
39mDeep Dive into Minikube
33mMinikube: Bringing Kubernetes to the Next Billion Users
33mMinikube: Bringing Kubernetes to the Next Billion Users
30mPhippy’s First Steps Into Kubernetes
35mDancing with Helm, Skaffold and Minikube!
32mLocal development techniques with Kubernetes