# Practice Bank: General Troubleshooting Operations

**Kubernetes Health Probes & Troubleshooting** and **The RootNode Troubleshooting Framework**
already taught you how to *think* about a broken cluster. This module is six short Labs that
drill the individual `kubectl` operations you'll reach for while doing that thinking: pulling
logs, copying files in and out of a container, running a one-off exec, cordoning a node, and
reasoning about pod-to-node placement and log output.

## How to use it

Work through the six Labs in order. None of them require the full Observe/Evidence/Hypothesis/
Test/Repair/Validate/Prevent framework from the previous module — they're deliberately narrower,
so you can build raw command fluency without also holding the whole framework in your head at
the same time.

## Instructor Notes

**Delivery:** No lesson/demonstration/knowledge-check scaffolding by design — this is the
original Phase 1-5 "troubleshooting" scenario bank plus one extra Lab (`container-logging-mcq`)
not part of that original set, reused here as self-paced speed practice.

**Capstone note:** The five original Labs (`extract-logs-basics`, `kubectl-cp-basics`,
`exec-command-basics`, `node-cordon-basics`, `pod-node-assignment-mcq`) are the exact set the
pre-existing `rootnode-path.json` "troubleshooting" 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.

**Common mistake to watch for:** running `kubectl cp` with the source/destination arguments
reversed — a good moment to have a student read the command back out loud before running it.