Why Minikube Isn't Enough Minikube is great for learning Kubernetes locally. But when you want to truly understand how a production cluster works — with a separate control plane and worker nodes, real inter-node networking, kubeadm managing the bootstrap — you need to go further. I built this course for people who want to experience the real Kubernetes architecture: not a simplified environment, but a multi-node cluster that mirrors what you'd find in a data center or on a cloud provider. The Environment: VirtualBox + Ubuntu Server You need at least 3 VMs: 1 control plane + 2 worker nodes, all running Ubuntu Server 22.04 LTS, with bridge networking for inter-node communication. Network configuration is often where people get stuck — I dedicate a full section to static IPs, /etc/hosts, and kubeadm prerequisites. System Prerequisites Every node needs: containerd as container runtime, swap disabled, kernel modules overlay and br_netfilter loaded, IP forwarding enabled, and ports 6443/2379-2380/10250-10259 open. Kubeadm Init: Bootstrapping the Control Plane kubeadm init --pod-network-cidr=10.244.0.0/16 — this single command bootstraps the control plane. The output gives you the kubeadm join command for worker nodes, kubectl configuration instructions, and the 24-hour join token. CNI: Pod Networking Without a CNI plugin, nodes stay in NotReady state. Install Flannel with a single kubectl apply and nodes become Ready within seconds. What's in the Course The Kubernetes Cluster Setup from Scratch course guides you through every step from VM configuration to a fully working cluster with worker nodes ready for real workloads.