ced4568andClaude Sonnet 5
f695b7c95d
- root-01-m00-welcome-to-root: program overview + Lab-lifecycle orientation (disposable Labs, permanent progress, hints, reset/recreate, help-requests). - One short intro-lesson activity for each of the three bare practice-bank modules (root-06-m01, root-07-m01, root-10-m02), explaining what the bank is and why it has no per-scenario teaching of its own — the minimum real authoring needed for genuine self-paced readiness without reclassifying them optional (see the curriculum migrations). Co-Authored-By: Claude Sonnet 5 <[email protected]>
2.2 KiB
Practice Bank: Deployments & Workloads
This module is different from the ones before it. There's no new lesson here — you already got the real teaching in Deployments, Scaling & Updates and Jobs, CronJobs & DaemonSets. This is eight short, focused Labs that drill the exact same skills at speed: deploy, scale, roll forward, add a liveness probe, edit a live object, and reason about Jobs/CronJobs/DaemonSets without a guided walkthrough alongside you.
Why this exists
Real fluency with kubectl comes from repetition, not from reading about it a second time. Each
Lab here is a small, self-contained task — no long setup, no new concepts — so you can move
quickly and build the kind of muscle memory that matters when you're troubleshooting a real
cluster under time pressure later in this program.
How to use it
Work through the eight Labs in order. If one takes you more than a few minutes, that's useful information — it usually means the earlier module's concept hasn't fully clicked yet, and it's worth a quick re-read of that lesson before continuing rather than pushing through by trial and error.
Instructor Notes
Delivery: This module has no lesson/demonstration/knowledge-check scaffolding by design — it is the original Phase 1-5 "workloads" scenario bank, reused here as a self-paced speed-practice set once the real teaching (root-06-m02/m03) has already landed. In an instructor-led cohort, this is a good candidate for a timed "workloads sprint" between the teaching modules and Jobs.
Capstone note: These eight scenarios are also the exact set the pre-existing
rootnode-path.json "workloads" stage requires to unlock the Capstone assessment (a separate,
older mechanism from this course's own prerequisite chain — see
docs/ROOT_V1_CURRICULUM_MANIFEST.md). Do not mark this module optional/is_required=false without
re-checking that gate; a student can only be told to skip it if the Capstone gate itself is
intentionally changed too.
Common mistake to watch for: students treating the MCQ-style activities (jobs-cronjobs-mcq, daemonset-mcq, deployment-strategy-mcq) as throwaway trivia — they're checking the same conceptual judgment calls the reflection in root-06-m03 raised, just faster.