ced4568andClaude Sonnet 5
60fbf0c385
Pre-Phase-1 platform work, approved and tested earlier but not yet committed: - Terminal banner: "RootNode Academy Lab — node: k8s-lab", upstream KubeKosh attribution left untouched in footer/README/LICENSE. - RootNode curriculum mode: scenarios/rootnode-path.json (Foundation -> Workloads -> Networking -> Configuration -> Troubleshooting -> Real Ops -> Capstone), built from existing scenario content grouped by category, no new scenarios invented. New GET /api/curriculum/path endpoint. - Student roster + per-student progress: instructor-roster, pick-your-name login (no password), students/environments-adjacent progress table migrated to a (student_id, scenario_id) composite key so practice progress and exam sessions are isolated per student instead of one global bucket. New /api/roster, /api/login endpoints. - scenarios/data/*.json: added isolation_type metadata (shared_namespace vs ephemeral_cluster) from an audit of which scenarios execute cluster-scoped or node-level commands. This was Tier-1-isolation groundwork that got superseded same-day by the full-ephemeral-per-student architecture (see docs/LAB_ARCHITECTURE.md) — the field is kept as descriptive metadata only, per the note now in scenarios/SCHEMA.md. Not wasted: it's an accurate audit of which scenarios touch cluster-scoped resources, useful independent of isolation model. - .gitignore added (node_modules/, frontend/dist/, *.db, /data/, .env) — none existed before; without it, npm installs during testing would have landed in a commit. Known limitation still open: no frontend UI for any of this yet (login screen, roster-add form, curriculum view) — API-only. No auth on the roster-add endpoint. Co-Authored-By: Claude Sonnet 5 <[email protected]>
46 lines
1.9 KiB
JSON
46 lines
1.9 KiB
JSON
{
|
|
"id": "pod-basics-mcq",
|
|
"title": "Pod Lifecycle States",
|
|
"category": "Core Concepts",
|
|
"isolation_type": "shared_namespace",
|
|
"difficulty": "Easy",
|
|
"type": "mcq",
|
|
"weight": 3,
|
|
"description": "## What does the `CrashLoopBackOff` status mean for a Pod?\n\nYou observe the following when running `kubectl get pods`:\n\n```\nNAME READY STATUS RESTARTS AGE\nmy-app-xyz 0/1 CrashLoopBackOff 5 3m\n```\n\nWhat is the Kubernetes control plane communicating with this status?",
|
|
"options": [
|
|
{
|
|
"id": "a",
|
|
"text": "The pod image could not be pulled from the container registry"
|
|
},
|
|
{
|
|
"id": "b",
|
|
"text": "The container starts, crashes, and Kubernetes keeps restarting it with exponential backoff delay"
|
|
},
|
|
{
|
|
"id": "c",
|
|
"text": "The pod is waiting for a PersistentVolume to become available"
|
|
},
|
|
{
|
|
"id": "d",
|
|
"text": "The pod has been evicted from the node due to resource pressure"
|
|
}
|
|
],
|
|
"correct_option": "b",
|
|
"explanation": "`CrashLoopBackOff` means the container is repeatedly crashing after startup. Kubernetes restarts it automatically but introduces increasing delays (backoff) between attempts to avoid overwhelming the system. Common causes include a bad entrypoint command, missing environment variables, or application errors on startup.",
|
|
"hints": [
|
|
{
|
|
"title": "Interpreting pod status",
|
|
"body": "Use `kubectl describe pod <name>` to see the Events section — it shows exactly why the container is failing.",
|
|
"command": "kubectl describe pod my-app-xyz"
|
|
},
|
|
{
|
|
"title": "Reading container logs",
|
|
"body": "Even a crashed container leaves logs behind. Use `--previous` to read the logs from the last crash.",
|
|
"command": "kubectl logs my-app-xyz --previous"
|
|
}
|
|
],
|
|
"setup_commands": [],
|
|
"default_namespace": "default",
|
|
"teardown_commands": []
|
|
}
|