Hey folks! I started diving into Kubernetes over the weekend, and it's definitely been a challenge. I've got some basic Ubuntu experience and a bit of Docker under my belt from using TrueNAS Scale, but I feel like I jumped into the deep end right away.
I've set up a small lab with four VMs: two control nodes (one on RHEL 9.6 and another on Windows Server 2025 for Jenkins), and two worker nodes (one on Windows Server 2025 and the other on RHEL 9.6). It's been a learning curve, especially since I'm exclusively using SSH now, which has helped me grasp Linux better than I expected.
However, I'm stuck trying to get Flannel up and running, and I might switch to Calico instead. I'm using this lab to test my Python library across different environments, but I rely heavily on AI for support.
Here's the question: how long does it typically take to learn Kubernetes fundamentals without AI? It feels overwhelming, given the need for knowledge in Linux, PowerShell scripting, networking basics, and other skills just to grasp the core concepts. If you've been through this, how long did it take for you to feel comfortable? I'm keen to keep learning, but I'm curious about others' timelines and experiences. Thanks!
5 Answers
Jumping into Kubernetes can feel like a lot, but if you approach it with smaller project goals, it gets less overwhelming. After two months, I felt pretty comfortable, but I'd already had some sysadmin experience. Using tools like Packer and GitOps (e.g., Flux) can also simplify things. Just remember that creating a good workflow is key to really understanding K8s.
I get where you're coming from! I just set up a cluster with two Ubuntu control nodes and two Windows Server worker nodes. I had to rely on official guides and some AI help too. Flannel was tricky, but Calico was straightforward for me. Just make sure to check your documentation—don’t take everything at face value!
I've found that mixing node OS can complicate things if you don’t have previous experience. I suggest using Kubespray for a more straightforward setup. AI can help you understand principles, but ensure you don't rely solely on it—dig into the documentation and clarify things when you get stuck. Building a solid foundational knowledge will pay off in the long run!
For me, it took a few days to set up my first cluster, and a couple of months to get my Certified Kubernetes Administrator (CKA) certification. The official Kubernetes documentation is super helpful, and I recommend writing your own guides as you learn—that's what solidified my understanding the most! Start with simple goals and build upon them, and soon you'll find your footing. Just remember to track your configuration changes through something like Git!
Learning Kubernetes can definitely feel daunting. The good news is that there's no right timeline—it really depends on how much time you spend with it. Personally, I focused on breaking things down into smaller parts, which helped me grasp the concepts better. I got a decent grasp of Kubernetes in about a year, but I'd still call myself a work in progress. It's a complex topic—especially when mixing OSes like Windows and Linux, so don't be too hard on yourself!
Thanks for sharing that! I definitely feel like breaking it down will help—I’ll keep that in mind moving forward.
Great tip on Kubespray! I’ll definitely check it out and work on grounding myself in the basics.