If you are new to this

A closing note, since teaching newcomers is half of why this lab exists.

You don't learn infrastructure by reading; you learn it by building something real and then having to keep it working. A home lab like this — a host, some VMs, a cluster, the supporting services — is the cheapest way to meet the actual problems: the firewall that blocks your cluster, the database that won't start, the certificate in the wrong place. Those problems are the curriculum.

A few suggestions if you want to follow this path:

• Build it yourself, the hard way, once. Use kubeadm, not a one-click cluster. Feel where the pieces join. Then use the easy tools knowing what they hide.
• Write down the why, not just the how. A copied command teaches nothing; the reason behind it is the transferable part. (This whole wiki is an attempt to practice that.)
• Expect to be wrong, and keep notes when you are. Every mistake page in this book started as an hour of confusion.
• Reach for the boring principle. Least privilege, one edge, plan capacity, make it reproducible, watch everything. They're boring because they work.

The tools will change. Kubernetes, Kong, Loki — all of it will look different in five years. The judgement won't. That's the thing worth building a lab to learn.