---
title: 'Stop Learning Kubernetes (Do This First)'
source: 'https://youtube.com/watch?v=keZN3i23qXs'
video_id: 'keZN3i23qXs'
date: 2026-08-19
duration_sec: 178
channel: 'TechWorld with Nana'
---

# Stop Learning Kubernetes (Do This First)

> Source: [Stop Learning Kubernetes (Do This First)](https://youtube.com/watch?v=keZN3i23qXs)

## Summary

The video argues that most DevOps job seekers over-prioritize deep Kubernetes knowledge, when in fact 70% of DevOps roles don't require it. The creator recommends a pragmatic learning path: start with cloud fundamentals, then infrastructure as code, then Docker, and only then learn basic Kubernetes concepts. The video concludes with a promotional offer for free orientation calls.

### Key Points

- **Kubernetes is overrated for most DevOps jobs** [00:02] — 70% of DevOps jobs do not require deep Kubernetes knowledge. Core skills are cloud fundamentals, CI/CD, and infrastructure as code.
- **Kubernetes is often a buzzword in job descriptions** [00:18] — Recruiters often list Kubernetes as a requirement simply because it's trendy, not because the project actually needs it.
- **Recommended learning order** [00:32] — Learn cloud concepts first, then infrastructure as code, then Docker, and finally basic Kubernetes (pods, deployments, services).
- **Basic Kubernetes is enough for most roles** [01:01] — Hands-on basics of Kubernetes are sufficient for 80% of roles. Deep expertise (operators, CRDs, cluster architecture) is only needed for specialized positions like Kubernetes administrator or platform engineer.
- **Don't let perfect be the enemy of good** [01:32] — You don't need to master Kubernetes to land your first DevOps role. Understanding 20% of fundamentals is enough to have a normal conversation in an interview.
- **Free orientation calls offer** [02:01] — The creator promotes free orientation calls for engineers to help them structure their learning path and identify immediate next steps.

### Conclusion

The key takeaway is to prioritize learning the fundamentals that matter most for DevOps roles, rather than diving deep into Kubernetes prematurely. Focus on cloud, CI/CD, and IaC first, and only learn basic Kubernetes unless you're targeting a specialized role.

## Transcript

DevOps. Well, that's actually not a correct advice for most people because here is a fact, 70% of DevOps jobs do not require deep Kubernetes knowledge. The required core skills for DevOps are
cloud fundamentals, CI/CD, and infrastructure as code. Even in job descriptions that mention Kubernetes, recruiters, they simply put Kubernetes in their job description just because it's a buzzword, not because the project
or company actually needs that skill. My recommendation is before you even get to Kubernetes, learn the cloud concepts first and then infrastructure as code and then dive deeper into container concepts with Docker. Once you have that
covered, learn just the fundamentals of Kubernetes, which is pods, deployments, services. Because if you're not a full-time Kubernetes administrator, you don't need to really deeply understand how the control plane components work.
But you do need to learn all those basics hands-on and that will be sufficient for 80% of the roles out there. And the deep expertise of Kubernetes, which is the operators, the custom controllers, CRDs, cluster
architecture, and so on, that's for specialized roles such as Kubernetes administrator or platform engineer or a senior DevOps engineer level, which are also paying pretty high salaries. So my advice is simply do not let perfect be
the enemy of good and know how to prioritize what skills you need to learn in which order. As I said, you don't need to master Kubernetes to land your first DevOps role. Understanding the 20% fundamentals will be enough to have a
normal conversation on a job interview about Kubernetes without having to be an expert. But this ties into a general problem that a lot of people have, which is you don't know where to start learning DevOps, what technologies and
learning DevOps, what technologies and tools to learn, and most importantly, to what level. And that's exactly why we decided for a short period of time to offer free orientation calls for engineers in our community all over the
world who want to figure out how to structure their learning to get from their current skills to where they want to go in the shortest amount of time. So, the main purpose of this call, which is absolutely free, is for you to have
enough clarity by the end of the call that you know what your immediate next that you know what your immediate next action step is going to be. So, if you want to take advantage of this temporary offer that we have, then make sure to
reserve your spot and understand what you need to do as a next step in your career. The link is going to be either in the comments or in the bio. So, check in the comments or in the bio. So, check that out and reserve your spot.