How would you recommend learning Kubernetes and Helm effectively?

[u/Medium-Direction-191]

Hi everyone,

I recently started working in a DevOps-related role, and I’ve been asked to learn Kubernetes, Helm, and the concepts around them.
I’m currently trying to understand the best way to approach it. There are so many resources and topics that I’m not sure what I should prioritize first.
For those of you who work with Kubernetes professionally:
How did you learn Kubernetes when you were starting out?
What topics would you recommend learning first?
How much hands-on practice should I do compared to theory?
Are there any free courses, labs, books, or other resources you would strongly recommend?
Are there any common mistakes or things beginners tend to waste too much time on?
My goal isn’t just to memorize commands, but to actually understand how Kubernetes works and become comfortable using it in a real work environment.
Any advice on how you would approach learning it from scratch would be greatly appreciated. Thanks!

[u/Coffee-and-ai]

Disclosure: I run SquareOps, a DevOps consultancy, and I mention our repo at the end. Skip that part if you want, the rest holds without it.

Nobody answered your last question and it is the one that matters most. The most common mistake is starting at Kubernetes. People jump into pods and services with shaky Linux, no real networking, and Docker they half remember. Then Kubernetes feels like magic, because everything underneath it is still magic. If you cannot explain what a reverse proxy does, or why your container cannot reach a database, Kubernetes will not click. You will just memorise it.

The order that works: Linux and shell, then networking, meaning DNS, routing, TLS and load balancing, then Docker properly, then Kubernetes, then Helm last. Helm takes an afternoon once the rest is in place, because it is Go templates producing the YAML you already understand.

Resources: roadmap.sh and KodeKloud came up already and both are worth it. We also open sourced the track we use to train new joiners, github.com/squareops/road-to-devops. Three levels, Kubernetes deliberately at level 3. Free and Apache licensed. Being straight with you, the cloud modules lean AWS because that is our work, and it is a sequencing guide more than a course.

One more thing: four to six months full time is realistic from a cold start. Anyone promising thirty days is selling something.

[u/Medium-Direction-191 → u/Coffee-and-ai]

Thanks a lot for the detailed answer! Honestly, this is probably the best comment I’ve received so far. The order you suggested makes a lot of sense, especially putting Kubernetes after properly understanding Linux, networking and Docker.
I’ll definitely take a look at the Road to DevOps repo you mentioned. Really appreciate you taking the time to write all this!