⚙️ Installing Kubernetes

Installing Kubernetes: Think of minikube as a driving-school car park and a cloud cluster as the motorway.

Think of minikube as a driving-school car park and a cloud cluster as the motorway. Both have the same steering wheel, the same gears, the same rules of the road — but in the car park nobody is hurt when you stall, and it costs nothing to try the manoeuvre again. Nobody learns to drive by joining rush-hour traffic on day one, and nobody should learn Kubernetes by provisioning a billed production cluster on day one. For learning and local development you do NOT need a real cloud cluster — minikube creates a single-node K8s cluster on your laptop in minutes. For production, cloud providers (AWS EKS, Google GKE, Azure AKS) manage the Control Plane for you instead. So why not just learn directly on a cloud cluster since that's what production actually uses? Because a cloud cluster costs money per hour and takes minutes to provision, while minikube boots locally in seconds and costs nothing to break — the same reason a Java developer runs unit tests against an in-memory H2 database before ever touching the real Postgres instance. The concepts (Pods, Services, Deployments) are IDENTICAL on minikube and EKS; only who manages the Control Plane changes. The QA risk worth knowing: a 'works on minikube' deployment can still fail on a real cloud cluster if it depends on node-specific storage or networking minikube doesn't enforce — always validate the YAML against a real cluster before calling it production-ready.

Local vs Cloud Options

Step 1: Install Docker Desktop (prerequisite)

Install Docker Desktop — required for minikube

Why Docker Desktop Install Is a Prerequisite for minikube

Package manager installs it

winget/brew/apt installs not Kubernetes, but the container engine minikube will run on top of.

WSL Integration enabled

On Windows, without Settings → Resources → WSL Integration enabled, minikube's docker driver cannot start containers.

docker --version verifies

This command proves the CLI can reach the daemon — if it can't, minikube start fails immediately.

docker run hello-world proves the entire image-pull-and-run chain works END TO END.

minikube's foundation is ready

minikube will build its own Kubernetes node on top of this WORKING Docker engine.