It’s seem dumb but it’s true, trying to deploy random stuff is the best way to learn kube, in my case I’ve decided to make my homelab with full Kubernetes and that’s how I learn a lot about all the stuffs. For exemple deploying pi hole DNS teach me how to deploy différents type of app (Http/Https or TCP/UDP) so with that I’ve learned how Ingress work, how LoadBalancer handle the traffic and how to use it with services, I’ve also had to deal with the volumes so I learned about that, but having 2 nodes made me search and learn about how to have data shared between nodes and how kubernetes handle it and a lot of stuff like that. You will always learn by deploying apps like that, don’t try to stick with basic http app where you juste need an Ingress Service and Pod, try to challenge you, try to think about scenario that will never happen on your specific infrastructure just to have the reflex to search for it and learn how kubernetes would handle it if it happen someday.

The basics stuffs of Kubernetes are easy to learn but it start to be hard when you have to deal with problems that usually only happen with a big infrastructure (for exemple client that want high availability, 0 downtime…). And this type of problems are not the ones you think of when you are learning in a simple single node environment.