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
1.9 KiB
JSON
53 lines
1.9 KiB
JSON
{
|
|
"id": "rolling-update-task",
|
|
"title": "Perform a Rolling Update",
|
|
"category": "Workloads",
|
|
"isolation_type": "shared_namespace",
|
|
"difficulty": "Easy",
|
|
"type": "task",
|
|
"weight": 5,
|
|
"description": "## Perform a Rolling Update\n\nA Deployment named `app-v1` is running `nginx:1.24`. Your team needs to upgrade it to `nginx:1.25`.\n\n**Your task:**\n\nUpdate the image of the `app-v1` deployment to `nginx:1.25` using a rolling update strategy. Ensure all replicas are running the new image.",
|
|
"hints": [
|
|
{
|
|
"title": "Set a new image on a Deployment",
|
|
"body": "Use `kubectl set image deployment/<name> <container-name>=<new-image>` to trigger a rolling update.",
|
|
"command": "kubectl set image deployment/app-v1 nginx=nginx:1.25"
|
|
},
|
|
{
|
|
"title": "Check rollout progress",
|
|
"body": "Monitor the rollout with `kubectl rollout status`. Once complete, all pods will run the new image.",
|
|
"command": "kubectl get deployment app-v1 -o jsonpath='{.spec.template.spec.containers[0].image}'"
|
|
}
|
|
],
|
|
"setup_commands": [
|
|
{
|
|
"command": "kubectl create deployment app-v1 --image=nginx:1.24 --replicas=2"
|
|
},
|
|
{
|
|
"command": "kubectl rollout status deployment/app-v1 --timeout=60s"
|
|
}
|
|
],
|
|
"validation": {
|
|
"commands": [
|
|
{
|
|
"description": "Deployment 'app-v1' image is nginx:1.25",
|
|
"command": "kubectl get deployment app-v1 -o jsonpath='{.spec.template.spec.containers[0].image}'",
|
|
"expected_output": "nginx:1.25",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "Deployment has 2 ready replicas",
|
|
"command": "kubectl get deployment app-v1 -o jsonpath='{.status.readyReplicas}' 2>/dev/null | grep -v '^$' || echo 0",
|
|
"expected_output": "2",
|
|
"match": "exact"
|
|
}
|
|
]
|
|
},
|
|
"default_namespace": "default",
|
|
"teardown_commands": [
|
|
{
|
|
"command": "kubectl delete deployment app-v1 --ignore-not-found"
|
|
}
|
|
]
|
|
}
|