Commit Graph

7 Commits

Author SHA1 Message Date
7fae1f2c36 chore: drop pause fields from recorded history, log attempt #11
Two things in one regeneration of the data files:

  - Stripped "pauses" and "paused_seconds" from all 10 existing entries, so the
    data matches the code change in 01877f0 rather than leaving historical
    telemetry behind. Nothing else in those entries was touched.
  - Attempt #11: Simulator Set C, 163/163. Recorded for completeness, but it is
    not a measure of skill - the tasks were completed programmatically to verify
    the new bank end to end on a freshly seeded cluster, not solved by hand.
    Set C tasks carry set="c" and are excluded from POOL, so this does not
    affect `./exam drill weak` or `./exam drill all` selection; `./exam sim c`
    re-runs the full set regardless of history.

The genuine result from this week is attempt #10: an 18-task drill at 39.7%,
8 of 11 attempted tasks at full credit, 7 never opened.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NziZdvBvy7CpEAAbZNgp8i
2026-09-20 17:35:49 -06:00
269f4d4ebb docs: updated history and weak-spots 2026-09-19 14:02:53 -06:00
69c8ec9557 docs: updated docs for current cka track. exam on Sat. 2026-09-16 19:48:09 -06:00
63e2503c59 chore: update drill history and weak-spots from today's ARCH/TSHOOT sessions
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-13 15:53:04 -06:00
58a357d7d2 feat: add kube-apiserver failure and node-join-verification tasks
Close two of the four CKA-relevant gaps identified against Killercoda's
scenario catalog:

- Q123 (TSHOOT, hard): kube-apiserver itself crash-loops on a static-pod
  manifest typo, same pattern as the existing scheduler/controller-manager
  failures (Q20/Q118) but with the added twist that kubectl is completely
  unusable until it's fixed, forcing node-level diagnosis (crictl,
  journalctl).
- Q124 (ARCH, hard): produce a real node-join handoff file by
  independently computing the CA discovery hash kubeadm join verifies
  against, and finding the API server's actual in-cluster address rather
  than the local kubeconfig's port-forwarded one.

Cluster-upgrade and operator-authoring remain unimplemented and are
documented as genuine infrastructure gaps in CKA_SOLUTIONS_EXPLAINED.md
(kind's node images have no apt-installable multi-version kubelet/kubeadm,
and operator authoring needs a real built/pushed image) rather than faked.

Also updates the Killercoda cross-reference table with the gaps closed,
and logs an ended drill session to history-cka.jsonl/weak-spots-cka.md.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-10 21:25:18 -06:00
ea6878066f docs: updated weak-spots and history files 2026-09-08 20:04:11 -06:00
99f833db68 docs: add history-cka and weak-spots for mental notes and to keep up with progression 2026-09-07 09:30:53 -06:00