Learn Kubernetes
For people who have to run Kubernetes, not just deploy to it.
What does the Learn Kubernetes track cover?
This track builds the mental model that makes Kubernetes behaviour predictable, then works through deployment strategy, monitoring, troubleshooting and what changes when you have more than a handful of clusters.
The route, in order
Control loops, the control plane, the kubelet, and why a successful apply does not mean it happened.
Pods, deployments, namespaces and the reconciliation model.
Rolling, blue/green and canary: what each protects against and what it costs.
The six signals that predict failure, and the many that only look useful.
A decision tree from pod status to cause, in the order that reaches it fastest.
What actually gets hard at fleet scale, and the patterns that hold up.
What you should be able to do afterwards
- Explain why Kubernetes behaves the way it does, from the reconciliation model
- Choose a deployment strategy per environment with reasons
- Diagnose Pending, CrashLoopBackOff, ImagePullBackOff and OOMKilled quickly
- Recognise which problems only appear once you have many clusters
Questions about this track
It assumes you have deployed something to Kubernetes and are comfortable with kubectl. If not, start with the glossary entries and come back.
No. It covers operating clusters rather than building them, on the reasonable assumption that most people use a managed service or an existing cluster.
Where to go next
Learn DevOps
Start here if DevOps is a word you use more confidently than you would like.
Learn observability
What each signal is for, how to make them join, and how to keep the bill sane.
Learn DevSecOps
The controls that reduce the most risk, in the order worth doing them.
Learn AI and agentic DevOps
Where agents genuinely help, where they are oversold, and how to introduce them safely.
Learn cloud operations
Running infrastructure across providers without three of everything.
See it working rather than reading about it
Connect a cluster read-only during a demo call and look at the concepts in your own environment.