Learn cloud operations
Running infrastructure across providers without three of everything.
What does the Learn cloud operations track cover?
This track covers building one operating model across cloud providers, understanding where Kubernetes money actually goes, and the infrastructure hygiene that quietly causes outages when neglected.
The route, in order
Why it happens, what it costs, and unifying the model rather than the services.
Requests versus usage, attribution, and right-sizing without causing incidents.
Declarative definitions, plan-and-apply, and drift.
Why continuous comparison matters more than detection at deploy time.
Finding the certificates nobody documented, before they expire.
What changes once the fleet outgrows a single-cluster operating model.
What you should be able to do afterwards
- Explain why a cluster can be 25% utilised and completely unschedulable
- Attribute cloud and Kubernetes cost to the teams that can change it
- Design one operating model that works across providers
- Find the certificates that are going to cause your next outage
Where this shows up in the product
Questions about this track
None. The material covers AWS, Azure and Google Cloud where specifics matter and stays provider-neutral otherwise.
Not a full one. It covers the Kubernetes and infrastructure side of cost, which is where most engineering-controllable spend sits.
Where to go next
Learn DevOps
Start here if DevOps is a word you use more confidently than you would like.
Learn Kubernetes
For people who have to run Kubernetes, not just deploy to it.
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.
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.