Command Palette

Search for a command to run...

Hectal
Phase 0Beginner1 of 10 in Kubernetes

The Kubernetes Mindset

Why running containers at scale needs an orchestrator at all, the architecture underneath every cluster, and your first real pod.

Docker's own course covered running ONE container, or a handful via Compose, on ONE machine. Kubernetes exists for the moment that stops being enough — dozens or hundreds of containers, spread across many machines, that need to be scheduled, healed, scaled, and networked automatically. This phase covers the model underneath every single kubectl command you'll ever type.

The same loop as every other course here: Learn → Close the tutorial → Explain without notes → Try it in a real terminal → Break it → Fix it → Explain the trade-off.

0/4 · 0%
4 topics ~55 min 7 code blocks & diagrams
Start with the first topic
1
0.1

Why Kubernetes: The Orchestration Problem

Running one container is easy; running hundreds across many machines, healing them when they crash, and scaling them under load is a genuinely hard problem — Kubernetes is the tool built specifically to solve it.

13 min 1 diagram practice

2
0.2

Architecture: Control Plane vs Worker Nodes

Every Kubernetes cluster splits into a control plane (the brain, making decisions) and worker nodes (the muscle, actually running your containers) — understanding this split explains where every component you'll learn actually lives.

14 min 1 diagram 1 code practice

3
0.3

Pods: The Smallest Deployable Unit

Kubernetes never schedules a container directly — it schedules a POD, a thin wrapper around one or more containers that always share the same network address and lifecycle.

14 min 1 diagram 2 code practice

4
0.4

Your First Cluster & kubectl

kubectl is your one tool for every interaction with a cluster — get, describe, apply, delete, and logs cover the overwhelming majority of what you'll type, on any cluster, for the rest of this course.

14 min 1 code practice