Getting started

Prerequisites

kubefit runs on macOS (Apple silicon or Intel) and Linux. What you need depends on the tracks you drill.

On macOS with Homebrew:

brew install kind kubernetes-cli helm lima

Give Docker enough resources for a three-node kind cluster: 4 CPUs and 6 GB of memory is comfortable. The LFCS VM asks for 2 CPUs, 3 GiB of memory and a 20 GiB disk, plus two 4 GiB practice disks.

Install the CLI

Early access builds are shared directly with invited members; a Homebrew tap and notarized releases are coming. Put the kubefit binary somewhere on your PATH, then check your tools:

kubefit doctor

doctor reports each tool as ok, missing (with the install command) or stopped when Docker is installed but its daemon is not running.

Sign in

kubefit login

The CLI prints a ten-character code and a link. Open the link, sign in to app.kubefit.com if you are not already, check that the code on the page matches your terminal, and approve. The CLI receives a token and stores it under ~/.kubefit. The code expires after ten minutes. See Account and sync for how tokens work.

Download packs

kubefit packs

Downloads and verifies every track's pack, or name the ones you want: kubefit packs cka lfcs. Packs are cached and refreshed when the site publishes a new version.

Your first drill

kubefit drill cka

The first run creates the muscle kind cluster, which takes a minute or two. kubefit then seeds an exercise, prints the task and opens a shell in the exercise directory with a status line before every prompt:

⏱ 00:42  kubefit task · kubefit grade · exit to finish

Work on the task. Run kubefit grade whenever you want a check. When you are done, exit the shell: kubefit confirms the final state, records the rep, and syncs it to your account. The exit check does not count as an extra attempt, so a single passing kubefit grade followed by exit is a cold pass.

Read Drills for everything the drill shell can do.