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]>
53 lines
2.3 KiB
JSON
53 lines
2.3 KiB
JSON
{
|
|
"id": "cronjob-task",
|
|
"title": "Create a CronJob",
|
|
"category": "Workloads & Scheduling",
|
|
"isolation_type": "shared_namespace",
|
|
"difficulty": "Easy",
|
|
"type": "task",
|
|
"weight": 4,
|
|
"description": "## Create a CronJob\n\nCronJobs create Jobs on a repeating schedule, perfect for maintenance tasks like log rotation, backups, or report generation.\n\n**Your task:**\n\nCreate a CronJob named `date-printer` that:\n- Runs **every minute** (`* * * * *`)\n- Uses `busybox:1.36`\n- Executes: `date`\n- Has `successfulJobsHistoryLimit: 3`",
|
|
"hints": [
|
|
{
|
|
"title": "CronJob manifest",
|
|
"body": "Use `kubectl create cronjob` and then patch with `successfulJobsHistoryLimit: 3`, or create a cronjob with a manifest. The schedule uses standard cron syntax.",
|
|
"command": "cat <<EOF | kubectl apply -f -\napiVersion: batch/v1\nkind: CronJob\nmetadata:\n name: date-printer\nspec:\n schedule: \"* * * * *\"\n successfulJobsHistoryLimit: 3\n jobTemplate:\n spec:\n template:\n spec:\n restartPolicy: OnFailure\n containers:\n - name: printer\n image: busybox:1.36\n command: [\"date\"]\nEOF"
|
|
}
|
|
],
|
|
"setup_commands": [],
|
|
"validation": {
|
|
"commands": [
|
|
{
|
|
"description": "CronJob 'date-printer' exists",
|
|
"command": "kubectl get cronjob date-printer -o jsonpath='{.metadata.name}'",
|
|
"expected_output": "date-printer",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "CronJob schedule is every minute",
|
|
"command": "kubectl get cronjob date-printer -o jsonpath='{.spec.schedule}'",
|
|
"expected_output": "* * * * *",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "CronJob uses busybox:1.36 image",
|
|
"command": "kubectl get cronjob date-printer -o jsonpath='{.spec.jobTemplate.spec.template.spec.containers[0].image}'",
|
|
"expected_output": "busybox:1.36",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "CronJob has successfulJobsHistoryLimit: 3",
|
|
"command": "kubectl get cronjob date-printer -o jsonpath='{.spec.successfulJobsHistoryLimit}'",
|
|
"expected_output": "3",
|
|
"match": "exact"
|
|
}
|
|
]
|
|
},
|
|
"default_namespace": "default",
|
|
"teardown_commands": [
|
|
{
|
|
"command": "kubectl delete cronjob date-printer --ignore-not-found"
|
|
}
|
|
]
|
|
}
|