00 / DevOps
Learn the daemon, the cluster and the pipelinegraded by the real tools
146 lessons planned, engineering complete, CI gate still ahead - status is exactly that, not softer.
01 / what grades you
Grading runs the real tools the job actually uses, in the copy of VS Code you already have open - not a simulated sandbox and not a recording.
When a lesson says PASSED, that verdict came from the real debugger, the real test runner, or a real service running on your machine.
02 / the free tier
DevOps is in development
There is no free tier to try yet - DevOps has not shipped a lesson. 146 lessons across 9 tracks are planned; the syllabus below is the plan of record for what ships.
03 / syllabus
146 lessons across 9 tracks
Troubleshooting
The container that died at 3am/Ten thousand lines, one clue/Two corpses, one killer/The flapping service/The failure that was not the failure/It is always DNS/First live patient/Two claimants, one port/The unreachable database/No space left on device/The secret nobody passed/Healthy app, unhealthy status/The corruption that survived redeploy/The connect that never refuses/The tag that moved/First pod on the slab/Scheduled: never/Three faults, one pager
Docker
Autopsy of an image/Fix the Dockerfile on paper/Build it for real/The rebuild that took forever/Names are not identities/Leave the toolchain behind/The 900 MB build context/Config in, secrets out/Data outlives containers/The dev loop/Speak by name/Teach docker what healthy means/Who restarts the restarter/The hog meets the cap/Two services, one file/Started is not ready/One stack, two lives/Your own registry/The size gate/Ship it as a container
Git for delivery
Short branches, straight trunk/Name the release/The changelog that cannot lie/One commit, one version/The gate before the commit/If it is red, it does not leave/Provenance or it did not happen/Fix once, land twice/Roll back in the open/Twenty commits, one culprit/Tags trigger ships/The artifact knows its commit/Ship only what changed/Cut the release
CI pipelines
Read a pipeline cold/Your first green run/No pushing to debug/Fire only when it matters/Nine legs, three that matter/One red leg must not hide the others/The key that went stale/Hand the build downstream/Jobs that talk/Cancel the obsolete run/The secret that echoed/The token can do too much/Keys nobody stores/Stop pasting steps/One pipeline, many callers/The twenty-dollar month/Retry is not a fix/The database beside the job/Measure before you matrix/The whole pipeline/Anatomy of a Jenkinsfile/Fix the broken Jenkinsfile/Credentials, agents and when-blocks/Translate a Jenkinsfile to a modern workflow
Kubernetes
The pod on the slab/Write the pod on paper/Make it real/Blast radius/Sets, not names/Declare three of them/Change without downtime/The revision that lied/A name inside the cluster/A door to the outside/One IP, many hosts/Config leaves the image/Secrets are not configmaps/Kill the deadlocked/Out of rotation, not dead/The OOM that keeps coming/Scratch space rules/Data outlives pods/The bad replica/Run to completion/On a schedule, no overlap/Can this account do that/The whole app in-cluster/Broken on arrival
Helm and GitOps
Three manifests, one truth/Chart from zero/Who wins/The indent that broke prod/Optional means absent/One label truth/Lint before install/First release/Revision two/Undo at the release level/Charts live in registries too/Reject bad values early/The reconcile loop/Be the controller
Terraform and IaC
The plan is the contract/Declare a file into being/Apply the plan, not the config/Typed inputs, guarded/Compute, then render/The graph does the ordering/Migrate without destroying/The state is a database/Someone edited prod by hand/Adopt the orphan/Fold the repetition/Inputs, outputs, nothing else/One config, two worlds/Protect the crown jewels/Retire one thing/Inherit the messy state
Enterprise reality
Routes versus ingress/oc to kubectl, mapped/SCCs versus pod security/Reading a DeploymentConfig/Templates versus Helm/Enterprise topology forensics
Ship it - capstone
Know what you ship/The Dockerfile on paper/The dev environment/The pipeline/Into the registry/Into the cluster/The release ritual/The incident/Undo in production/Ship it, all of it
04 / how it grades you
Do the work
Open the lesson in VS Code and write the fix, the query, or the test - in your own editor, with your own tools.
The real tool checks it
The debugger, the test runner, or the real service your code talks to decides pass or fail - not a string match on your keystrokes.
Hints, then the solution
Stuck lessons escalate through hints before the reference solution unlocks - spoilers are earned, not browsable.
05 / your machine
What to expect on your machine
By track, per operating system
| Track | Windows | macOS | Linux |
|---|---|---|---|
| Full curriculum | not yet | not yet | not yet |
| No per-OS rows yet, honestly: all 146 lessons are written, but the CI gate has not run. Measured operating-system rows land here after the first full gate, and not before. | |||
measuring, 2026-08-30
TO BE VERIFIED Windows, macOS, Linux
Per-operating-system expectations are published here once the CI gate has run - measured, with run ids, the way the shipped products do it. Nothing is claimed before then.
06 / receipts
Receipts
Receipts land when this ships. TESTED first, receipts with it - that is the order.