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]>
58 lines
2.3 KiB
JSON
58 lines
2.3 KiB
JSON
{
|
|
"id": "namespaces-basics",
|
|
"title": "Working with Namespaces",
|
|
"category": "Core Concepts",
|
|
"isolation_type": "shared_namespace",
|
|
"difficulty": "Easy",
|
|
"type": "task",
|
|
"weight": 4,
|
|
"description": "## Working with Namespaces\n\nNamespaces provide a mechanism for isolating groups of resources within a single cluster.\n\n**Your task:**\n\n1. Create a namespace called `team-alpha`\n2. Deploy a `nginx:alpine` Deployment named `web` with **2 replicas** inside the `team-alpha` namespace\n\n**Verify your work:**\n```bash\nkubectl get namespace team-alpha\nkubectl get deployment web -n team-alpha\n```",
|
|
"hints": [
|
|
{
|
|
"title": "Create a namespace",
|
|
"body": "Use `kubectl create namespace <name>` to create a new namespace.",
|
|
"command": "kubectl create namespace team-alpha"
|
|
},
|
|
{
|
|
"title": "Deploy into a specific namespace",
|
|
"body": "Use the `-n` or `--namespace` flag with `kubectl create deployment`. Alternatively use `kubectl apply -f` with `namespace` set in the manifest metadata.",
|
|
"command": "kubectl create deployment web --image=nginx:alpine --replicas=2 -n team-alpha"
|
|
}
|
|
],
|
|
"setup_commands": [],
|
|
"validation": {
|
|
"commands": [
|
|
{
|
|
"description": "Namespace 'team-alpha' exists",
|
|
"command": "kubectl get namespace team-alpha -o jsonpath='{.metadata.name}'",
|
|
"expected_output": "team-alpha",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "Deployment 'web' exists in team-alpha",
|
|
"command": "kubectl get deployment web -n team-alpha -o jsonpath='{.metadata.name}'",
|
|
"expected_output": "web",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "Deployment 'web' has 2 replicas",
|
|
"command": "kubectl get deployment web -n team-alpha -o jsonpath='{.spec.replicas}'",
|
|
"expected_output": "2",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "Deployment uses nginx image",
|
|
"command": "kubectl get deployment web -n team-alpha -o jsonpath='{.spec.template.spec.containers[0].image}'",
|
|
"expected_output": "nginx",
|
|
"match": "contains"
|
|
}
|
|
]
|
|
},
|
|
"default_namespace": "default",
|
|
"teardown_commands": [
|
|
{
|
|
"command": "kubectl delete namespace team-alpha --ignore-not-found --wait=false"
|
|
}
|
|
]
|
|
}
|