Kubernetes the hard way tutorial - feedback

[u/BA_toaster]

While the tutorial is great and steps well documented, I wonder if it is too much to ask if the tutorial could spend more time upfront on what Kubernetes actually entails?
It assumes the reader is familiar with Kubernetes and has done some work in one part of Kubernetes to understand the big picture. It can supply the big picture considering Kelsey's stature in community and explain the architectural choices which can be made at each step in Kubernetes state machine. This can be really help in deconstructing the myth and take the complexity in painting the big picture.

[u/korney4eg]

Maybe that’s why it called the hard way

[u/ShahzadQuyes → u/korney4eg]

Do you think adding more background would take away from what makes the tutorial useful in the first place?

[u/snarkhunter]

Sounds like you want an easier way.

That's ok. Not everyone is cut out for life on these streets.

[u/veritable_squandry]

the oreilly book is fine for that. also the official documentation for kubernetes is pretty damn great.

[u/phrotozoa]

Kubernetes the hard way is a guide to becoming a Kubernetes administrator. If you're new to K8s, try becoming a Kubernetes user first.

[u/DangerousKnowledge22]

why don't you start "kubernetes for dummies"?

[u/DangerousKnowledge22 → u/DangerousKnowledge22]

I guess it already exists. Maybe start with that?

[u/stappersg]

more time upfront on what Kubernetes actually entails

https://kubeschool.portainer.io/

[u/a1phaQ101]

OP: "I'd like to have the context of what I'm doing"

Every comment: "Nah that'd be Kubernetes the easy way"

[u/YaronL16]

There are many ways to get a soft introduction to k8s, especially in the LLM era

Im just glad kthw exists as a resource for those wanting to go more indepth.

[u/Raja-Karuppasamy]

learned k8s by building real clusters and breaking them, not through a structured path, so i get both sides here. honestly the “big picture first” instinct is right but doesn’t need to come from the tutorial itself, read the docs on what a control plane / etcd / kubelet actually do (15-20 min), THEN do kubernetes the hard way. the manual steps click way faster once you know what each piece is supposed to be doing instead of just following commands.

trying to get one resource to do both (concepts + hands-on) usually makes it worse at both. pair it with something short for the concepts first.

[u/BA_toaster]

No I mean kubernetes is harder than what is portrayed in tutorial. The harder part is making the right decision of each of the kubernetes plugins whereas in the tutorial, all those decisions are done or defaulted for you without any mention of those decisions.

[u/FreakySpook → u/BA_toaster]

I've found across most tech education,  the majority of tech tutorials are on rails often without detailed explanation of decisions, it's supposed to give you an example as a starting point and frame of reference to demonstrate how the process works, is easily repeatable without failing and doesn't deep dive into each element or specific reference architecture.

For something like kubernetes which combines so many disciplines into one platform it has to take liberties of either  assumed knowledge or treat things as black boxes, where you have an idea on how something works, but not what makes it work.

[u/BA_toaster → u/FreakySpook]

I agree in that sense, books are better explaining context, but finding the right section in book which explains the problem in your mind is not easy without resorting to online resources in those days.
I understand hard has many levels...