Files
rootnode-academy/scenarios/data/nodeport-task.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

54 lines
2.1 KiB
JSON

{
"id": "nodeport-task",
"title": "Expose a Deployment via NodePort",
"category": "Services & Networking",
"isolation_type": "shared_namespace",
"difficulty": "Easy",
"type": "task",
"weight": 5,
"description": "## Expose a Deployment via NodePort\n\nA **NodePort** service exposes an application on a static port on every node, making it accessible outside the cluster without a cloud load balancer.\n\n**Your task:**\n\nA deployment `frontend` is already running. Expose it as a **NodePort** service named `frontend-np` on:\n- Service port `80`\n- NodePort `30080`\n- Target port `80`",
"hints": [
{
"title": "Create NodePort service",
"body": "Use `kubectl expose` or apply a Service manifest with `type: NodePort` and the `nodePort` field.",
"command": "cat <<EOF | kubectl apply -f -\napiVersion: v1\nkind: Service\nmetadata:\n name: frontend-np\nspec:\n type: NodePort\n selector:\n app: frontend\n ports:\n - port: 80\n targetPort: 80\n nodePort: 30080\nEOF"
}
],
"setup_commands": [
{
"command": "kubectl create deployment frontend --image=nginx:alpine --replicas=1 2>/dev/null || true"
}
],
"validation": {
"commands": [
{
"description": "Service 'frontend-np' exists",
"command": "kubectl get service frontend-np -o jsonpath='{.metadata.name}'",
"expected_output": "frontend-np",
"match": "exact"
},
{
"description": "Service type is NodePort",
"command": "kubectl get service frontend-np -o jsonpath='{.spec.type}'",
"expected_output": "NodePort",
"match": "exact"
},
{
"description": "NodePort is 30080",
"command": "kubectl get service frontend-np -o jsonpath='{.spec.ports[0].nodePort}'",
"expected_output": "30080",
"match": "exact"
}
]
},
"default_namespace": "default",
"teardown_commands": [
{
"command": "kubectl delete deployment frontend --ignore-not-found"
},
{
"command": "kubectl delete svc frontend-np --ignore-not-found"
}
]
}