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]>
59 lines
2.3 KiB
JSON
59 lines
2.3 KiB
JSON
{
|
|
"id": "annotate-resource-basics",
|
|
"title": "Annotating Kubernetes Resources",
|
|
"category": "Core Concepts",
|
|
"isolation_type": "shared_namespace",
|
|
"difficulty": "Easy",
|
|
"type": "task",
|
|
"weight": 3,
|
|
"description": "## Annotating Kubernetes Resources\n\nAnnotations attach arbitrary non-identifying metadata to Kubernetes objects — such as contact info, tool versions, or documentation URLs. Unlike labels, annotations **cannot** be used as selectors.\n\n**Your task:**\n\nA Deployment named `myapp` is running in the `default` namespace. Add the following annotations to it:\n- `[email protected]`\n- `reviewed=true`\n\n```bash\n# Verify:\nkubectl get deployment myapp -o jsonpath='{.metadata.annotations}'\n```",
|
|
"hints": [
|
|
{
|
|
"title": "kubectl annotate",
|
|
"body": "Use `kubectl annotate` to imperatively add or overwrite annotations on any resource.",
|
|
"command": "kubectl annotate deployment myapp [email protected] reviewed=true"
|
|
},
|
|
{
|
|
"title": "Overwrite an existing annotation",
|
|
"body": "If the annotation key already exists, pass `--overwrite` to update it.",
|
|
"command": "kubectl annotate deployment myapp [email protected] reviewed=true --overwrite"
|
|
}
|
|
],
|
|
"setup_commands": [
|
|
{
|
|
"command": "kubectl create deployment myapp --image=nginx:alpine --replicas=1 2>/dev/null || true"
|
|
},
|
|
{
|
|
"command": "kubectl rollout status deployment/myapp --timeout=60s"
|
|
}
|
|
],
|
|
"validation": {
|
|
"commands": [
|
|
{
|
|
"description": "Deployment 'myapp' exists",
|
|
"command": "kubectl get deployment myapp -o jsonpath='{.metadata.name}'",
|
|
"expected_output": "myapp",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "Annotation 'contact' is [email protected]",
|
|
"command": "kubectl get deployment myapp -o jsonpath='{.metadata.annotations.contact}'",
|
|
"expected_output": "[email protected]",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "Annotation 'reviewed' is true",
|
|
"command": "kubectl get deployment myapp -o jsonpath='{.metadata.annotations.reviewed}'",
|
|
"expected_output": "true",
|
|
"match": "exact"
|
|
}
|
|
]
|
|
},
|
|
"default_namespace": "default",
|
|
"teardown_commands": [
|
|
{
|
|
"command": "kubectl delete deployment myapp --ignore-not-found"
|
|
}
|
|
]
|
|
}
|