A lightweight, local Kubernetes environment that runs entirely on a single machine, without containers or virtual machines. The kminus stack bundles a real Kubernetes control plane (API server, etcd and controller manager) with a virtual kubelet that runs pods as native processes, which gives a fast and minimal Kubernetes for development and testing.
It holds the orchestration components of tabsdata:
native-process pods (km). Every local tabsdata instance runs on it.
| Component | Language | What it does |
|---|---|---|
| control‑plane | Go | Starts a local Kubernetes control plane Runs kube‑apiserver, etcd, kube‑controller‑manager Writes the kubeconfigs of the administrator and the components |
| virtual‑kubelet | Go | Registers as a node in the cluster Runs the pods as native processes on the host, not in containers |
| pod‑runner | Rust | Manages the lifecycle of each pod as native host processes |
| kminus | Rust | The distribution binary, kmStarts the other components as child processes Orchestrates them |
Build kminus first, as Developing KMinus describes. The binaries land in
target/dist.
Create an instance in a folder that doesn't exist yet.
macOS and Linux:
./target/dist/km create --workdir ~/km-demoWindows:
.\target\dist\km.exe create --workdir $HOME\km-demoStart it. The command stays in the foreground until you stop the instance, so leave this terminal open and use another one for the next steps.
macOS and Linux:
./target/dist/km start --workdir ~/km-demoWindows:
.\target\dist\km.exe start --workdir $HOME\km-demoPoint kubectl at the instance, and apply a manifest.
macOS and Linux:
export KUBECONFIG=~/km-demo/config/kubeconfig.yaml./target/dist/kubectl apply -f examples/deployment.yamlWindows:
$env:KUBECONFIG = "$HOME\km-demo\config\kubeconfig.yaml".\target\dist\kubectl.exe apply -f examples\deployment.yamlCheck the instance, and stop it when you're done.
macOS and Linux:
./target/dist/km status --workdir ~/km-demo./target/dist/km stop --workdir ~/km-demoWindows:
.\target\dist\km.exe status --workdir $HOME\km-demo.\target\dist\km.exe stop --workdir $HOME\km-demoThe examples explain the conventions a pod must follow to run on kminus.
The kminus stack is meant to be built and used together with tabsdata, checked out side by side. Its Developing Tabsdata guide covers the software to install, the clone, the build environment and the toolchain.
Developing KMinus adds what is specific to this repository: its layout, its tasks, its build profiles and its tests.
- Control Plane
- Virtual Kubelet
- Pod Runner: User Guide
- Pod Runner: Implementation
- KMinus: Component Messages
- KMinus: Readiness and Liveness
Licensed under the Apache License, Version 2.0.