Module 6
Operations
A platform is judged by how calmly it upgrades, how fast it scales, how clearly you can see it, and what it costs. These are routines, not projects.
Why it matters. Teams that rehearse upgrades and watch cost and saturation weekly rarely have incidents. Teams that skip them have a quarterly crisis.
After this module you can answer
- In what order do I upgrade, and how do I avoid downtime?
- In-place or blue and green node upgrades?
- How do Pods and nodes scale together?
- Which observability stack should I run?
- Where does EKS money actually go, and what can I cut?
What is inside
1Upgrade sequence
2In-place vs blue/green
3Pre-upgrade checks
4Scaling pods and nodes
5Observability
6Cost optimisation
7GitOps
8Tenancy patterns
9Module infographic