K3s
TAS Score: S3/3 – D5/5 – A3 / T2
Brief Description
Lightweight certified Kubernetes distribution built for edge, IoT, and resource‑constrained environments. Single binary, low memory footprint, fully offline capable.
Architectural Role
Compute orchestration layer: manages containers across a cluster. Provides scheduling, service discovery, secrets management, and declarative application deployment.
Technical Autonomy
- ✅ Works without internet (after installation and image pull)
- ✅ Stores data locally (etcd, manifests, local storage)
- ✅ Does not require external accounts
- ✅ Allows data export (cluster state can be backed up)
- ✅ Provides offline updates (manual upgrade via script or package)
Philosophical Assessment (whose.world criteria)
| Criterion | Status | Comments |
|---|---|---|
| Pause | Yes | Cluster can be stopped (stop the k3s service); workloads can be paused. |
| Exit | Yes | No vendor lock‑in; workloads can be exported or moved to other Kubernetes clusters. |
| Recoverability | Yes | Regular etcd snapshots allow full cluster recovery. |
| Visibility | Yes | Open source, fully transparent. |
| External Dependencies | Yes | No required cloud services; can run in air‑gapped mode. |
Configuration (Minimal)
Single‑node server install (on Debian/Ubuntu):
curl -sfL https://get.k3s.io | sh -
Verify it works offline (after installation and pulling images):
sudo k3s kubectl get nodes
For air‑gapped environments, use the offline installation guide.
Related Recipes
- Minimal Autonomous Server – can be extended with K3s for full orchestration.
Alternatives
- K0s – another lightweight Kubernetes distribution.
- MicroK8s – Canonical’s lightweight Kubernetes (requires snap).
- Nomad – HashiCorp orchestrator, simpler but less declarative.
Sources
-
Docker image
-
Community -e
Trajectory
Mixed — CNCF sandbox, Rancher/SUSE backed.
K3s is developed by Rancher (acquired by SUSE). It is in the CNCF sandbox. Corporate backing means sustained development, but also means the project follows SUSE’s business interests. Watch for: enterprise-only features, or deprioritisation if SUSE strategy shifts. Rate: stable, monitor.