devops

The hands-on version. Deploy the same database twice, delete a pod each time, and watch it vanish once and survive once, with the output you should see at every step.

What each one is, how you ask for it, when to reach for which, and why the difference decides whether your data is still there after a pod restarts.

I froze on a kubectl command Mischa asked about. It felt exactly like building a sentence in Portuguese. Both are grammar, and that changed how I learn.

How a request finds your app in Kubernetes. Ingress routes by host and path, a Service load-balances across pods with a stable address, and the pod answers. With a hands-on k3s demo you can run yourself.

One of the first things I picked up, and one of the few I still reach for every single day. From your first connection to logging in with a single word.

You're a junior sysadmin, your manager just dropped "migrate everything to containers by end of sprint" in Slack, and you Google'd what is a container. Welcome. Let's actually fix that.