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]>
47 lines
1.9 KiB
JSON
47 lines
1.9 KiB
JSON
{
|
|
"id": "job-task",
|
|
"title": "Create a One-Shot Job",
|
|
"category": "Workloads & Scheduling",
|
|
"isolation_type": "shared_namespace",
|
|
"difficulty": "Easy",
|
|
"type": "task",
|
|
"weight": 4,
|
|
"description": "## Create a One-Shot Job\n\nA **Job** creates one or more pods and ensures a specified number of them successfully terminate. Unlike Deployments, Jobs are meant for finite tasks that run to completion.\n\n**Your task:**\n\nCreate a Job named `pi-job` that:\n- Uses `perl:5.34` image\n- Runs: `perl -Mbignum=bpi -wle 'print bpi(100)'` (computes π to 100 digits)\n- `completions: 1`\n- `restartPolicy: Never`",
|
|
"hints": [
|
|
{
|
|
"title": "Job manifest",
|
|
"body": "Set `restartPolicy: Never` or `OnFailure` in the pod template spec (not at pod spec level).",
|
|
"command": "cat <<EOF | kubectl apply -f -\napiVersion: batch/v1\nkind: Job\nmetadata:\n name: pi-job\nspec:\n completions: 1\n template:\n spec:\n restartPolicy: Never\n containers:\n - name: pi\n image: perl:5.34\n command: [\"perl\",\"-Mbignum=bpi\",\"-wle\",\"print bpi(100)\"]\nEOF"
|
|
}
|
|
],
|
|
"setup_commands": [],
|
|
"validation": {
|
|
"commands": [
|
|
{
|
|
"description": "Job 'pi-job' exists",
|
|
"command": "kubectl get job pi-job -o jsonpath='{.metadata.name}'",
|
|
"expected_output": "pi-job",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "Job completions is 1",
|
|
"command": "kubectl get job pi-job -o jsonpath='{.spec.completions}'",
|
|
"expected_output": "1",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "Job restartPolicy is Never",
|
|
"command": "kubectl get job pi-job -o jsonpath='{.spec.template.spec.restartPolicy}'",
|
|
"expected_output": "Never",
|
|
"match": "exact"
|
|
}
|
|
]
|
|
},
|
|
"default_namespace": "default",
|
|
"teardown_commands": [
|
|
{
|
|
"command": "kubectl delete job pi-job --ignore-not-found"
|
|
}
|
|
]
|
|
}
|