Lesson 2 of 4 · Free to read
Exercises
Exercises — Production Capstone & Portfolio
Watch & learn
Course video
Course video
Keep a lab notebook: hypothesis → command → result. Speed without evidence is not a skill.
How to use this file
- Work Lab A → B → C on the same
orders-labrepo - Prefer Docker Desktop; use Kind when the lab says so
- Definition of Done at the bottom is the phase gate
Lab A — Lineage map
Time: 45–60 min
Goal: One architecture diagram spanning phases 01–09.
Setup
Your orders-lab repo history.
Steps
- Draw current system + telemetry planes.
- Annotate which phase added each capability.
- List certs/topics you are now ready to study (PCA/OTCA/CKA) as optional next steps.
Success criteria
- Diagram + phase legend committed
If stuck
Use mermaid if you lack a drawing tool.
Lab B — Final game day
Time: 60–90 min
Goal: Telemetry-only diagnosis under chaos.
Setup
SLOs + Chaos Mesh or scripted faults.
Steps
- Pick two faults from your catalog.
- Diagnose using dashboards/traces/profiles only.
- Update postmortem or add a short addendum.
Success criteria
- Diagnosis notes without SSH claims
- SLO impact recorded
If stuck
If stuck, narrow to one fault — depth beats breadth.
Lab C — Portfolio + talk track
Time: 60 min
Goal: Public-ready evidence pack.
Setup
GitHub repo (public or private with export).
Steps
- Write
PORTFOLIO.mdwith links to dashboards-as-code, policies, chaos catalog, postmortem. - Draft a 5-minute talk script.
- Optional stretch: document EKS migration checklist without requiring deploy.
Success criteria
- PORTFOLIO.md complete
- Talk script rehearsed once
If stuck
Screenshot dashboards if live demos are flaky — evidence still counts.
Stretch goals
- Deploy to real EKS if you have credits — still optional
- Write a short blog post on one RCA
Definition of Done
- Portfolio README exists
- Final game day documented
- You can narrate metric→trace→profile without notes
Exercises — Production Capstone & Portfolio.