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": "cks-rbac-clusterrole",
|
|
"title": "Cluster-Level RBAC",
|
|
"category": "Cluster Security",
|
|
"isolation_type": "ephemeral_cluster",
|
|
"difficulty": "Medium",
|
|
"type": "task",
|
|
"weight": 5,
|
|
"description": "## Cluster Roles and Bindings\n\nSome resources, like Nodes, are cluster-scoped and cannot be accessed using normal Roles and RoleBindings.\n\n**Your task:**\n\n1. Create a ServiceAccount named `monitor-sa` in the `monitoring` namespace.\n2. Create a ClusterRole named `node-viewer` that grants `get`, `list`, and `watch` permissions on `nodes`.\n3. Create a ClusterRoleBinding named `monitor-node-binding` to bind the ClusterRole to the ServiceAccount.\n\n```bash\n# Verify your permissions:\nkubectl auth can-i list nodes --as=system:serviceaccount:monitoring:monitor-sa\n```",
|
|
"hints": [
|
|
{
|
|
"title": "Imperative Commands",
|
|
"body": "Create the SA, then the ClusterRole, then the ClusterRoleBinding.",
|
|
"command": "kubectl create sa monitor-sa -n monitoring && kubectl create clusterrole node-viewer --verb=get,list,watch --resource=nodes && kubectl create clusterrolebinding monitor-node-binding --clusterrole=node-viewer --serviceaccount=monitoring:monitor-sa"
|
|
}
|
|
],
|
|
"setup_commands": [
|
|
{
|
|
"command": "kubectl create namespace monitoring --dry-run=client -o yaml | kubectl apply -f -"
|
|
}
|
|
],
|
|
"validation": {
|
|
"commands": [
|
|
{
|
|
"description": "monitor-sa exists in monitoring namespace",
|
|
"command": "kubectl get sa monitor-sa -n monitoring -o jsonpath='{.metadata.name}'",
|
|
"expected_output": "monitor-sa",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "ServiceAccount can list nodes",
|
|
"command": "kubectl auth can-i list nodes --as=system:serviceaccount:monitoring:monitor-sa",
|
|
"expected_output": "yes",
|
|
"match": "exact"
|
|
}
|
|
]
|
|
},
|
|
"default_namespace": "default",
|
|
"teardown_commands": [
|
|
{
|
|
"command": "kubectl delete sa monitor-sa -n monitoring --ignore-not-found"
|
|
},
|
|
{
|
|
"command": "kubectl delete clusterrole node-viewer --ignore-not-found"
|
|
},
|
|
{
|
|
"command": "kubectl delete clusterrolebinding monitor-node-binding --ignore-not-found"
|
|
}
|
|
]
|
|
}
|