Tracks

Every track is a signed pack: its exercises, setup scripts, graders and the shared lab helpers. kubefit packs downloads them all.

Cluster profiles

Kubernetes tracks run on kind with the same node image for every drill.

• base creates the muscle cluster: one control plane and two workers. CKA, CKAD, CNPE, ICA and OPS share it.
• cks creates muscle from a hardened configuration with audit logging and encryption-at-rest mounts, so the CKS scenarios see the node names and files they expect.
• ckne creates muscle-ckne with no default CNI, and the track pins its own kubeconfig context so Cilium can be installed and inspected.

kubefit records which profile built a cluster and refuses to run a drill whose profile does not match. Run kubefit end first and let the next drill rebuild.

Add-ons a track needs, such as the NGINX ingress controller, Gateway API, metrics-server, MetalLB, Cilium, Multus, seccomp profiles or the CNPE stack, install once per cluster the first time a drill needs them.

LFCS

LFCS drills run inside a Lima virtual machine named kubefit-lfcs: Ubuntu 24.04, 2 CPUs, 3 GiB of memory, a 20 GiB system disk and two blank 4 GiB disks for storage exercises. The drill shell is a root shell inside the VM with kubefit-grade, kubefit-task and kubefit-abandon available. Storage and kernel exercises run in the VM, never on your host. kubefit end deletes the VM and its disks.

Exam-allowed documentation

Each task ends with the documentation pages that answer it, limited to the sites the exam lets you open. kubefit task prints them. The track's guide on the site lists the allowed sites.