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]>
53 lines
2.2 KiB
JSON
53 lines
2.2 KiB
JSON
{
|
|
"id": "cks-rbac-least-privilege",
|
|
"title": "RBAC Least Privilege",
|
|
"category": "Cluster Security",
|
|
"isolation_type": "shared_namespace",
|
|
"difficulty": "Medium",
|
|
"type": "task",
|
|
"weight": 4,
|
|
"description": "## Role-Based Access Control\n\nService Accounts should only be granted the permissions they explicitly need.\n\n**Your task:**\n\nCreate a Role named `pod-reader` in the `default` namespace that only allows the verbs `get`, `list`, and `watch` on the `pods` resource. Then, bind this Role to a ServiceAccount named `read-only-sa` using a RoleBinding named `read-only-binding`.\n\n```bash\n# Verify your RBAC setup:\nkubectl auth can-i list pods --as=system:serviceaccount:default:read-only-sa\n```",
|
|
"hints": [
|
|
{
|
|
"title": "Imperative commands",
|
|
"body": "You can create all 3 resources using imperative commands: create serviceaccount, create role, create rolebinding.",
|
|
"command": "kubectl create sa read-only-sa && kubectl create role pod-reader --verb=get,list,watch --resource=pods && kubectl create rolebinding read-only-binding --role=pod-reader --serviceaccount=default:read-only-sa"
|
|
}
|
|
],
|
|
"setup_commands": [],
|
|
"validation": {
|
|
"commands": [
|
|
{
|
|
"description": "ServiceAccount read-only-sa exists",
|
|
"command": "kubectl get sa read-only-sa -o jsonpath='{.metadata.name}'",
|
|
"expected_output": "read-only-sa",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "Role allows list pods",
|
|
"command": "kubectl auth can-i list pods --as=system:serviceaccount:default:read-only-sa",
|
|
"expected_output": "yes",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "Role denies delete pods",
|
|
"command": "kubectl auth can-i delete pods --as=system:serviceaccount:default:read-only-sa",
|
|
"expected_output": "no",
|
|
"match": "exact"
|
|
}
|
|
]
|
|
},
|
|
"default_namespace": "default",
|
|
"teardown_commands": [
|
|
{
|
|
"command": "kubectl delete sa read-only-sa --ignore-not-found"
|
|
},
|
|
{
|
|
"command": "kubectl delete role pod-reader --ignore-not-found"
|
|
},
|
|
{
|
|
"command": "kubectl delete rolebinding read-only-binding --ignore-not-found"
|
|
}
|
|
]
|
|
}
|