Reference-first learning
ClusterForge Academy publishes course pathways the way platform teams publish internal manuals: explicit prerequisites, reproducible steps, and candid notes about what exams omit. The sections below mirror a documentation landing page—quickstart, changelog, and community signals—while every deep dive still routes to live clusters.
We maintain formal relationships with training partners and CNCF-aligned tooling vendors so lab images stay current without surprise license drift.
Quick cluster context
# Connect to lab context
kubectl config use-context lab-clusterforge
kubectl get nodes -o widePick streams; we bundle digests weekly KST.
| Vertical | Focus | Subscribe |
|---|---|---|
| Release radar | Kubernetes minor notes and lab compatibility | |
| CKS watchlist | Admission, runtime, and supply-chain briefings | |
| Team playbooks | Enablement templates for platform squads |
Independent editors, guild newsletters, and buyer-side research desks reference our materials when describing how certification prep should sound: specific about time, honest about scope, and careful with exam boundaries. We do not pay for placement; excerpts below come from public commentary patterns we are allowed to summarize. When in doubt, we prefer quieter language over loud claims. The accordion keeps the page scannable for engineers reviewing the site between incidents.
“ClusterForge’s changelog-style release notes helped our guild decide when to skip a minor bump without sounding alarmist.”
“Their weekend bootcamp write-up was blunt about time cost, which is rare in this space and appreciated by our buyers.”
“We quoted their lab disclaimer language almost verbatim when drafting our own student agreements.”
Each note pairs a learner experience with a measurable habit shift we observed during programs.
The CKA Cluster Operations Lab fault tree forced me to narrate kubelet decisions aloud; our guild now uses the same cadence during incidents, trimming redundant status checks.
Minji · 4.8/5 · Verified learner
CKAD UI-Agnostic Sprint broke my dashboard dependency; pairing sessions surfaced two kubectl aliases I still ship in PR descriptions.
Metric: reduced average PR review round-trips on manifest changes from six to four during the month after the sprint.
Ravi · Busan
Weekend intensive pacing was aggressive, yet the annotated NetworkPolicy homework from week two became our team’s reference when onboarding interns.
Metric: internal doc clicks on NetworkPolicy guidance rose steadily after the cohort without extra tooling spend.
Chen · Daejeon
Mock Exam Coaching Studio debriefs highlighted where I re-read prompts; I still set a silent timer during practice exams.
Metric: self-tracked mock completion time variance narrowed across three attempts without rushing remediation steps.
Nadia Rahman · Platform lead · Regional logistics
Team Enablement Foundations gave us a shared vocabulary for quota conversations; the facilitator notes were reusable verbatim in CAB packets.
Metric: CAB packets now attach lab-derived evidence snippets in nine of twelve monthly reviews post-program.
We ship curriculum metadata the same way platform teams ship control-plane migrations: semantic versions, explicit dates, and a flag when learners must replay a lab from a clean namespace. The table below is the friendly strip we mirror inside the private learner portal.
| Version | Release date | Migration required | Notes |
|---|---|---|---|
| 2.6.0 | 2026-04-18 | Yes | CKS supply-chain cards adopt Sigstore vocabulary refresh. |
| 2.5.2 | 2026-03-02 | No | CKAD sprint adds narrated kubectl review rubric. |
| 2.5.0 | 2026-01-20 | Yes | Lab ingress class renamed to match upstream annotations. |