kubernetes deployment framework

From laptopto production.One loop.

One CLI, one folder convention — the same commands carry a cluster from local kind to bare-metal production. No rewrite at the border.

Get started Concepts GitHub

The loop is the product

A cluster is a folder named by its FQDN. The folder doesn't care where it runs — only the driver changes.

cluster.lok8s.yaml
One folder per FQDN. Spec, targets, secrets — committed.
lo up
kind cluster with mirrors, TLS, bootstrap waves, Tilt.
lo provision
Same folder, real driver — CAPI or KubeOne on Hetzner.
lo status
Health, targets, GitOps — and back to define.

See it run

Docker is the only prerequisite — b installs the rest.

lok8s — local cluster in one command

What's in the box

driverskind for local & CI · Cluster API · KubeOne · KKP
bootstrapordered addon waves with health gates — Cilium, MetalLB, yours
dev loopTilt live-reload, pull-through mirrors, trusted local TLS
secretsdeterministic kustomize generator — cache-first, SHA-pinned
bare metalHetzner Robot via rescue + installimage, next to cloud VMs
agentsevery command doubles as an MCP tool with safety annotations

Close the loop.

Start on your laptop today. Keep the folder when it's time for real servers.

Get started CLI reference