Files
rootnode-academy/scenarios/data/broken-deployment.json
T
ced4568andClaude Sonnet 5 60fbf0c385 feat(curriculum): add RootNode learning path, student roster, and scenario isolation metadata
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]>
2026-08-18 01:21:16 -05:00

59 lines
2.3 KiB
JSON

{
"id": "broken-deployment",
"title": "Debug a Failing Deployment",
"category": "Troubleshooting",
"isolation_type": "shared_namespace",
"difficulty": "Medium",
"type": "task",
"weight": 8,
"description": "## Fix the Broken Deployment\n\nA deployment has been pre-created in the `debug` namespace but its pods are not running.\n\n**Your task:** Identify the problem and fix it so that the deployment has **all 3 pods in Ready state**.\n\n> Start by describing the deployment and its pods to find clues about what's wrong.",
"hints": [
{
"title": "Inspect the deployment",
"body": "Start by listing pods in the debug namespace and describing the failing ones.",
"command": "kubectl get pods -n debug\nkubectl describe pod -n debug -l app=broken-app"
},
{
"title": "Check events",
"body": "The Events section in `kubectl describe` usually tells you exactly what's wrong — look for ImagePullBackOff, OOMKilled, or probe failures.",
"command": "kubectl describe deployment broken-app -n debug"
},
{
"title": "Fix the image tag",
"body": "If the image tag doesn't exist, update it to a valid one using `kubectl set image`.",
"command": "kubectl set image deployment/broken-app nginx=nginx:1.25 -n debug"
}
],
"setup_commands": [
{
"command": "kubectl create namespace debug"
},
{
"command": "kubectl create deployment broken-app --image=nginx:invalid-tag-99999 --replicas=3 -n debug"
}
],
"validation": {
"description": "Checks that the broken-app deployment in the debug namespace has 3 ready replicas.",
"commands": [
{
"description": "Deployment 'broken-app' has 3 ready replicas",
"command": "kubectl get deployment broken-app -n debug -o jsonpath='{.status.readyReplicas}' 2>/dev/null | grep -v '^$' || echo 0",
"expected_output": "3",
"match": "exact"
},
{
"description": "No pods in ImagePullBackOff state",
"command": "kubectl get pods -n debug --no-headers 2>/dev/null | awk '{print $3}' | grep -c 'ImagePullBackOff\\|ErrImagePull' || true",
"expected_output": "0",
"match": "exact"
}
]
},
"default_namespace": "debug",
"teardown_commands": [
{
"command": "kubectl delete namespace debug --ignore-not-found --wait=false"
}
]
}