ChaGPT added lab simulations
This commit is contained in:
@@ -4,7 +4,7 @@ Canonical progress record for CKS preparation. Update this file after every grad
|
||||
|
||||
## Dashboard
|
||||
|
||||
Last updated: 2026-08-26
|
||||
Last updated: 2026-08-27
|
||||
|
||||
| Domain | Weight | Hero | Training | Not started | Total |
|
||||
|---|---:|---:|---:|---:|---:|
|
||||
@@ -38,6 +38,15 @@ A topic becomes Hero only when every item is checked:
|
||||
|
||||
Minor syntax corrections during training are expected. A cold retest fails when the solution needs field-by-field coaching, grants excess privilege, breaks required behavior, omits proof, or changes resources outside scope.
|
||||
|
||||
## Exam-Simulation Rules
|
||||
|
||||
- Every graded question is a Linux command-line lab on a designated host or Kubernetes context.
|
||||
- Prompts specify an end state; the learner changes files, resources, processes, or policies to reach it.
|
||||
- Deliverables are the resulting state plus short command/output evidence. Essays, prose tables, PowerShell parsing, and multiple-choice answers are not graded tasks.
|
||||
- Tools are used directly when the syllabus names them. A scanner task requires running the scanner and changing the system, not writing about scanner theory.
|
||||
- Harder-than-exam means more interacting controls, realistic faults, or a tighter time limit. It does not mean more literature questions.
|
||||
- When the current computer lacks the required Linux/Kubernetes environment, mark the task environment-blocked and use a Linux lab; do not replace it with a written substitute.
|
||||
|
||||
## Resume Protocol
|
||||
|
||||
1. Read `MISSION.md`, `NOTES.md`, the newest learning record, and this file.
|
||||
@@ -49,7 +58,19 @@ Minor syntax corrections during training are expected. A cold retest fails when
|
||||
|
||||
## Next Task
|
||||
|
||||
`CS-02.Q1` in progress as Lesson 0036: run a kube-bench-based CIS review and separate automated findings from manual checks across kube-apiserver, etcd, kubelet, and CoreDNS.
|
||||
Finish the one-time local lab installation after Windows restarts, then run `CS-02.Q1` as revised Lesson 0036 on `kind-cks-lab`. Do not use the learner's Kubernetes v1.36 production cluster: kube-bench v0.16.0 has automatic version mappings only through v1.34.
|
||||
|
||||
## Local Lab Environment
|
||||
|
||||
Status: `WINDOWS RESTART REQUIRED`
|
||||
|
||||
- Platform: Ubuntu 24.04 on WSL2, Docker Engine, two-node Kind cluster, and Calico.
|
||||
- Kubernetes: pinned to v1.34.0; kube-bench: pinned to v0.16.0.
|
||||
- Cluster and context: `cks-lab` / `kind-cks-lab`.
|
||||
- Kubeconfig: `/opt/cks-lab/kubeconfig`; it is never merged with a production config.
|
||||
- Setup and recovery files: `lab-environment/`.
|
||||
- Resume after restart: run `lab-environment\\02-install-and-build.ps1`, then `lab-environment\\verify-lab.ps1`.
|
||||
- Lesson scope: use Kind nodes for Kubernetes tasks and the disposable Ubuntu WSL2 VM for host/kernel hardening tasks.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user