Kubernetes for Absolute Beginners

If Docker is a shipping container, Kubernetes is the port: it decides where to put each container, restarts them if they fall, and moves them if a truck breaks down.

Why do we need it?

One or two containers on one machine — you can do it by hand. But when you have 200 containers spread across 30 machines, you need a manager. That manager is Kubernetes (often shortened to k8s).

The seven words

Word	Meaning
Node	A single machine (VM or physical) that runs containers.
Cluster	A group of nodes managed together.
Pod	The smallest unit — one (or a few tightly coupled) containers.
Deployment	Says "I want 3 copies of this pod running always".
Service	A stable network address that points to a set of pods.
Namespace	A folder that keeps environments separated (dev, staging, prod).
kubectl	The command-line tool to talk to a cluster.

Your first pod

my-pod.yaml:

apiVersion: v1
kind: Pod
metadata:
  name: hello
spec:
  containers:
    - name: web
      image: nginx:latest
      ports:
        - containerPort: 80

kubectl apply -f my-pod.yaml
kubectl get pods
kubectl port-forward pod/hello 8080:80

Open http://localhost:8080 — congratulations, you just ran your first pod!

Real-world analogy

Think of Kubernetes as Uber for containers. You say "I need 5 rides to the airport" (5 pods of my app). Uber (Kubernetes) figures out which cars (nodes) to use, tracks them, and if a car breaks down, sends a new one automatically.

Where to learn next

Deployments, Services and ConfigMaps — the next article in this series.