When you actually need this

Kubernetes runs containers across a group of machines, deciding where each runs, restarting what fails, and routing traffic to what is healthy.

It is genuinely powerful and genuinely heavy, and the most useful thing this course can do first is tell you when not to use it.

You do not need it for one application on one server, a small number of services with steady traffic, a team with no operations capacity, or anything a managed platform service already runs for you. Kubernetes for a single small application adds far more work than it removes, and it is adopted that way frequently because it is what people have heard of.

You do need it when you are running many services, when different parts must scale independently, when you need deployments with no downtime across many instances, when several teams deploy to shared infrastructure, or when your organisation has already standardised on it, which is the most common honest reason.

Learn it anyway if you want infrastructure work, because it appears in a large share of DevOps job adverts and being unable to discuss it closes doors regardless of whether the role needs it.

Use a managed service rather than running the control plane yourself. Every major cloud offers one, and operating your own cluster is a specialist job that adds nothing for most organisations.

And learn containers properly first, because Kubernetes assumes them and somebody learning both at once struggles unnecessarily.