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]>
55 lines
2.4 KiB
JSON
55 lines
2.4 KiB
JSON
{
|
|
"id": "secrets-basics",
|
|
"title": "Creating and Using Secrets",
|
|
"category": "Configuration",
|
|
"isolation_type": "shared_namespace",
|
|
"difficulty": "Easy",
|
|
"type": "task",
|
|
"weight": 5,
|
|
"description": "## Creating and Using Secrets\n\nSecrets let you store sensitive data (passwords, tokens, keys) separately from your pod specs.\n\n**Your task:**\n\n1. Create a Secret named `app-secret` with the key `api-key` and value `supersecret`\n2. Create a Pod named `secret-reader` using `busybox:1.36` that:\n - Mounts the secret key `api-key` as an environment variable named `API_KEY`\n - Runs: `sleep 3600`\n\n**Verify:**\n```bash\nkubectl exec secret-reader -- env | grep API_KEY\n```",
|
|
"hints": [
|
|
{
|
|
"title": "Create the Secret",
|
|
"body": "Use `kubectl create secret generic` with `--from-literal`.",
|
|
"command": "kubectl create secret generic app-secret --from-literal=api-key=supersecret"
|
|
},
|
|
{
|
|
"title": "Reference secret in a Pod env var",
|
|
"body": "Use `env[].valueFrom.secretKeyRef` in the container spec to map a secret key to an env var.",
|
|
"command": "cat <<EOF | kubectl apply -f -\napiVersion: v1\nkind: Pod\nmetadata:\n name: secret-reader\nspec:\n containers:\n - name: reader\n image: busybox:1.36\n command: [\"sleep\",\"3600\"]\n env:\n - name: API_KEY\n valueFrom:\n secretKeyRef:\n name: app-secret\n key: api-key\nEOF"
|
|
}
|
|
],
|
|
"setup_commands": [],
|
|
"validation": {
|
|
"commands": [
|
|
{
|
|
"description": "Secret 'app-secret' exists",
|
|
"command": "kubectl get secret app-secret -o jsonpath='{.metadata.name}'",
|
|
"expected_output": "app-secret",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "Pod 'secret-reader' is Running",
|
|
"command": "kubectl get pod secret-reader -o jsonpath='{.status.phase}'",
|
|
"expected_output": "Running",
|
|
"match": "exact"
|
|
},
|
|
{
|
|
"description": "Pod references the secret via env var",
|
|
"command": "kubectl get pod secret-reader -o jsonpath='{.spec.containers[0].env[0].valueFrom.secretKeyRef.name}'",
|
|
"expected_output": "app-secret",
|
|
"match": "exact"
|
|
}
|
|
]
|
|
},
|
|
"default_namespace": "default",
|
|
"teardown_commands": [
|
|
{
|
|
"command": "kubectl delete secret app-secret --ignore-not-found"
|
|
},
|
|
{
|
|
"command": "kubectl delete pod secret-reader --ignore-not-found --grace-period=0 --force"
|
|
}
|
|
]
|
|
}
|