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]>
51 lines
2.2 KiB
JSON
51 lines
2.2 KiB
JSON
{
|
|
"id": "limitrange-task",
|
|
"title": "LimitRange for Default Container Limits",
|
|
"category": "Workloads & Scheduling",
|
|
"isolation_type": "shared_namespace",
|
|
"difficulty": "Medium",
|
|
"type": "task",
|
|
"weight": 6,
|
|
"description": "## LimitRange\n\nA **LimitRange** sets default resource requests/limits for containers in a namespace. Any container created without explicit limits will automatically get the LimitRange defaults.\n\n**Your task:**\n\nCreate a namespace `bounded-ns` and a LimitRange named `default-limits` that sets:\n- Default CPU limit: `200m`\n- Default CPU request: `100m`\n- Default Memory limit: `256Mi`\n- Default Memory request: `128Mi`",
|
|
"hints": [
|
|
{
|
|
"title": "LimitRange manifest",
|
|
"body": "Use `type: Container` and the `default`/`defaultRequest` fields inside `spec.limits[]`.",
|
|
"command": "cat <<EOF | kubectl apply -f -\napiVersion: v1\nkind: LimitRange\nmetadata:\n name: default-limits\n namespace: bounded-ns\nspec:\n limits:\n - type: Container\n default:\n cpu: \"200m\"\n memory: \"256Mi\"\n defaultRequest:\n cpu: \"100m\"\n memory: \"128Mi\"\nEOF"
|
|
}
|
|
],
|
|
"setup_commands": [
|
|
{
|
|
"command": "kubectl create namespace bounded-ns 2>/dev/null || true"
|
|
}
|
|
],
|
|
"validation": {
|
|
"commands": [
|
|
{
|
|
"description": "LimitRange 'default-limits' exists in bounded-ns",
|
|
"command": "kubectl get limitrange default-limits -n bounded-ns -o jsonpath='{.metadata.name}'",
|
|
"expected_output": "default-limits",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "Default CPU limit is 200m",
|
|
"command": "kubectl get limitrange default-limits -n bounded-ns -o jsonpath='{.spec.limits[0].default.cpu}'",
|
|
"expected_output": "200m",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "Default memory limit is 256Mi",
|
|
"command": "kubectl get limitrange default-limits -n bounded-ns -o jsonpath='{.spec.limits[0].default.memory}'",
|
|
"expected_output": "256Mi",
|
|
"match": "exact"
|
|
}
|
|
]
|
|
},
|
|
"default_namespace": "bounded-ns",
|
|
"teardown_commands": [
|
|
{
|
|
"command": "kubectl delete namespace bounded-ns --ignore-not-found --wait=false"
|
|
}
|
|
]
|
|
}
|