Initially, I tried doing this with a 2010 Mac Mini (which claims to support VMX), but couldn't get Minikube running on it...
For the past two weeks though, I haven't had any issues with this setup on the Macbook Air!
For the past two weeks though, I haven't had any issues with this setup on the Macbook Air!
I though Kubernetes was all about containers, not VMs?
Why not just boot proper Linux on that thing?
Even on Linux, minikube uses a separate VM. It's just cleaner than having the kubelet running on your workstation directly. (microk8s takes a different approach and runs on your machine directly. The last time I interacted with it, it destroyed my coworker's workstation and we had to reinstall the machine completely. k8s is pretty invasive and really wants an entire machine at its disposal. VMs are just perfect for that.)
Thus my question: If the aim is to use the machine for a Kubernetes "cluster", why not boot proper Linux on it, so Kubernetes can run at full speed, without any VM overhead?
I think right now if you want to have a single-node testing cluster, you will be very happy with minikube and the VM it creates. If you want multiple nodes, you will be very happy with VMs; you can create, destroy, and inject errors right from the command-line without having to walk over to physical machines and manipulate them.
When I tried with minikube, the VirtualBox VM would boot successfully, but there was an issue with the networking b/w the VM and MacOS