One binary with the web dashboard embedded. No Go toolchain, no Node, no build step — download it, verify it, and run the loop.
Docker needs at least 4 CPUs and 8 GB of memory. labctl init runs a 3-node cluster plus the full platform stack; the 2 GB a fresh Docker VM ships with is not enough, and it fails as confusing TLS handshake timeout errors partway through. On macOS raise it in Docker Desktop → Resources, or start Colima with --cpu 4 --memory 8.
Or use the scripted install below, which detects your OS and architecture and verifies the checksum for you.
# Set the version you want, then run the block as-is.
VERSION=1.2.0
OS=$(uname -s | tr '[:upper:]' '[:lower:]') # darwin | linux
ARCH=$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/') # amd64 | arm64
BASE="https://github.com/sagar2395/snowopslabs/releases/download/v${VERSION}"
curl -fsSL "${BASE}/labctl_${VERSION}_${OS}_${ARCH}.tar.gz" -o labctl.tar.gz
curl -fsSL "${BASE}/checksums.txt" -o checksums.txt
# Verify before you trust it.
(command -v sha256sum >/dev/null && sha256sum -c checksums.txt --ignore-missing) \
|| shasum -a 256 -c checksums.txt --ignore-missing
tar xzf labctl.tar.gz labctl
sudo mv labctl /usr/local/bin/
labctl --versionlabctl runs scripts from scenarios/, platform/ and runtimes/ at runtime, so the release archive is not standalone. The binary just saves you installing Go and Node.
git clone https://github.com/sagar2395/snowopslabs.git
cd snowopslabs
cp config/.env.example .envlabctl doctor # is your machine ready? fixes printed inline
labctl init # cluster + platform stack
labctl scenario list
labctl ui # dashboard at http://localhost:3939Every published release, newest first.
A usability-focused release: the full "Autoscaling Under Load" UX audit remediation plus platform, observability, application, and lab-reset improvements — and the new SnowOps Labs brand. Each artifact below is the labctl CLI with the web UI embedded — one self-contained binary per platform.
app deploy now imports the local image into k3d/kind (building it first if missing) before deploying — no more ImagePullBackOff on a fresh cluster.$NAMESPACE / $DOMAIN_SUFFIX / $SCRIPT_DIR / $VALUES_FILE inline and show a variables legend explaining every value (secrets included).chaos.<domain> — no manual port-forward.labctl lab reset and the top-level labctl reset), in proper order — no more stale "active" state against a fresh cluster.Download the archive for your platform below (verify against checksums.txt), or follow the README Quickstart.
Full changelog: https://github.com/sagar2395/snowopslabs/compare/v1.0.0...v1.1.0
One real Kubernetes failure a week — the symptom, the commands that found it, and the fix. Written from actual lab runs, not from memory.
Signups aren't open yet — set NEXT_PUBLIC_NEWSLETTER_ENDPOINT to the Kit form endpoint to switch this on.
You'll get the Kubernetes Incident Response Field Guide, plus occasional emails about new scenarios, posts and paid offerings such as courses and workshops. Unsubscribe any time.