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]>
60 lines
2.9 KiB
JSON
60 lines
2.9 KiB
JSON
{
|
|
"id": "cks-egress-namespace",
|
|
"title": "Restrict Egress to Namespace",
|
|
"category": "Network Security",
|
|
"isolation_type": "shared_namespace",
|
|
"difficulty": "Hard",
|
|
"type": "task",
|
|
"weight": 6,
|
|
"description": "## Namespace-Scoped Egress Network Policy\n\nFine-grained network policies can restrict pod traffic so that only pods within a specific namespace can communicate with each other.\n\n**Your task:**\n\nA namespace `frontend` and a namespace `backend` already exist. Create a NetworkPolicy named `allow-backend-only` in the `frontend` namespace that:\n\n- Applies to **all pods** in the `frontend` namespace\n- **Allows egress only** to pods in the `backend` namespace (matched by `namespaceSelector`)\n- **Denies all other egress** traffic\n\n```bash\n# Verify:\nkubectl get networkpolicy allow-backend-only -n frontend\n```",
|
|
"hints": [
|
|
{
|
|
"title": "namespaceSelector in Egress rule",
|
|
"body": "Use `spec.policyTypes: [Egress]` with an empty egress rule except for a `namespaceSelector` that matches the `backend` namespace label.",
|
|
"command": "cat <<EOF | kubectl apply -f -\napiVersion: networking.k8s.io/v1\nkind: NetworkPolicy\nmetadata:\n name: allow-backend-only\n namespace: frontend\nspec:\n podSelector: {}\n policyTypes:\n - Egress\n egress:\n - to:\n - namespaceSelector:\n matchLabels:\n kubernetes.io/metadata.name: backend\nEOF"
|
|
}
|
|
],
|
|
"setup_commands": [
|
|
{
|
|
"command": "kubectl create namespace frontend --dry-run=client -o yaml | kubectl apply -f -"
|
|
},
|
|
{
|
|
"command": "kubectl create namespace backend --dry-run=client -o yaml | kubectl apply -f -"
|
|
}
|
|
],
|
|
"validation": {
|
|
"commands": [
|
|
{
|
|
"description": "NetworkPolicy 'allow-backend-only' exists in frontend namespace",
|
|
"command": "kubectl get networkpolicy allow-backend-only -n frontend -o jsonpath='{.metadata.name}'",
|
|
"expected_output": "allow-backend-only",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "Policy type is Egress only",
|
|
"command": "kubectl get networkpolicy allow-backend-only -n frontend -o jsonpath='{.spec.policyTypes[0]}'",
|
|
"expected_output": "Egress",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "Policy uses namespaceSelector targeting backend namespace",
|
|
"command": "kubectl get networkpolicy allow-backend-only -n frontend -o jsonpath='{.spec.egress[0].to[0].namespaceSelector.matchLabels.kubernetes\\.io/metadata\\.name}'",
|
|
"expected_output": "backend",
|
|
"match": "exact"
|
|
}
|
|
]
|
|
},
|
|
"default_namespace": "frontend",
|
|
"teardown_commands": [
|
|
{
|
|
"command": "kubectl delete networkpolicy allow-backend-only -n frontend --ignore-not-found"
|
|
},
|
|
{
|
|
"command": "kubectl delete namespace frontend --ignore-not-found --wait=false"
|
|
},
|
|
{
|
|
"command": "kubectl delete namespace backend --ignore-not-found --wait=false"
|
|
}
|
|
]
|
|
}
|