Completed upto lesson 28

2026-08-23 15:29:06 +06:00
parent fb86f0b60a
commit 8e43c00cd6
104 changed files with 1888 additions and 0 deletions
--- a/reference/cks-four-week-field-guide.html
+++ b/reference/cks-four-week-field-guide.html
@@ -0,0 +1 @@
+<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>CKS four-week field guide</title><link rel="stylesheet" href="../assets/course.css"></head><body><main><p class="eyebrow">Quick reference</p><h1>CKS: four-week field guide</h1><p class="lede">Your job is now practice-to-proof, not course-to-course.</p><h2>Operating rhythm</h2><ul><li><strong>5 days/week:</strong> 60–90 minutes hands-on; begin with 10 minutes of closed-book recall.</li><li><strong>1 day/week:</strong> a 90–120 minute mixed, timed set and an error review.</li><li><strong>1 day/week:</strong> rest or 20-minute flash review. Do not turn every day into a mock exam.</li></ul><h2>Four-week sequence</h2><ol class="plan"><li><strong>Week 1 — Workload security:</strong> Pod Security Admission, security contexts, capabilities, seccomp/AppArmor, service accounts, RBAC.</li><li><strong>Week 2 — Cluster and supply chain:</strong> API-server and kubelet hardening, encryption, audit policy, image provenance/scanning, admission controls.</li><li><strong>Week 3 — Network and runtime:</strong> NetworkPolicy (ingress + egress), mTLS concepts, Falco-style detection and incident triage.</li><li><strong>Week 4 — Performance:</strong> two full simulations, targeted re-drills from your error log, then light review and sleep protection.</li></ol><h2>Every task: the 5-step loop</h2><ol><li>Read the exact requirement; identify the control plane, namespace, workload, or node scope.</li><li>Inspect before changing: <code>kubectl get</code>, <code>describe</code>, <code>auth can-i</code>, logs, or the relevant manifest.</li><li>Apply the smallest compliant change.</li><li>Verify behavior, not only YAML syntax.</li><li>Record one mistake or shortcut in an error log.</li></ol><div class="callout"><strong>Confidence rule:</strong> confidence comes from completed, verified tasks. Track evidence: task, time used, first-try result, correction.</div><p>Use the <a href="https://github.com/cncf/curriculum/blob/master/CKS_Curriculum%20v1.34.pdf">official CKS curriculum</a> to map each task, and the <a href="https://training.linuxfoundation.org/certification/certified-kubernetes-security-specialist/">Linux Foundation exam page</a> for current logistics.</p></main></body></html>
				`@@ -0,0 +1 @@`
				<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>CKS four-week field guide</title><link rel="stylesheet" href="../assets/course.css"></head><body><main><p class="eyebrow">Quick reference</p><h1>CKS: four-week field guide</h1><p class="lede">Your job is now practice-to-proof, not course-to-course.</p><h2>Operating rhythm</h2><ul><li><strong>5 days/week:</strong> 60–90 minutes hands-on; begin with 10 minutes of closed-book recall.</li><li><strong>1 day/week:</strong> a 90–120 minute mixed, timed set and an error review.</li><li><strong>1 day/week:</strong> rest or 20-minute flash review. Do not turn every day into a mock exam.</li></ul><h2>Four-week sequence</h2><ol class="plan"><li><strong>Week 1 — Workload security:</strong> Pod Security Admission, security contexts, capabilities, seccomp/AppArmor, service accounts, RBAC.</li><li><strong>Week 2 — Cluster and supply chain:</strong> API-server and kubelet hardening, encryption, audit policy, image provenance/scanning, admission controls.</li><li><strong>Week 3 — Network and runtime:</strong> NetworkPolicy (ingress + egress), mTLS concepts, Falco-style detection and incident triage.</li><li><strong>Week 4 — Performance:</strong> two full simulations, targeted re-drills from your error log, then light review and sleep protection.</li></ol><h2>Every task: the 5-step loop</h2><ol><li>Read the exact requirement; identify the control plane, namespace, workload, or node scope.</li><li>Inspect before changing: <code>kubectl get</code>, <code>describe</code>, <code>auth can-i</code>, logs, or the relevant manifest.</li><li>Apply the smallest compliant change.</li><li>Verify behavior, not only YAML syntax.</li><li>Record one mistake or shortcut in an error log.</li></ol><div class="callout"><strong>Confidence rule:</strong> confidence comes from completed, verified tasks. Track evidence: task, time used, first-try result, correction.</div><p>Use the <a href="https://github.com/cncf/curriculum/blob/master/CKS_Curriculum%20v1.34.pdf">official CKS curriculum</a> to map each task, and the <a href="https://training.linuxfoundation.org/certification/certified-kubernetes-security-specialist/">Linux Foundation exam page</a> for current logistics.</p></main></body></html>