K3s is a lightweight Kubernetes distribution: a certified Kubernetes packaged as one binary of less than 100 MB, with the control plane, container runtime and the usual add-ons already included. The project describes it as easy to install with half the memory of a standard cluster, aimed at edge, homelab, IoT, continuous integration, development, ARM boards and air-gapped sites. K3s is free and open source under the Apache 2.0 licence, and it runs on Linux.
For a sysadmin the attraction is that a working single-node cluster can be installed with one command on a small server or virtual machine, while the same K3s can later be joined into a multi-node or high-availability cluster. The price is that you still run Kubernetes: upgrades, backups, certificates and network rules stay your job.
K3s at a glance
| Item | Details |
|---|---|
| Latest release | v1.37.2+k3s1 (3 November 2026), the K3s build of Kubernetes 1.37.2 |
| Licence | Free and open source, Apache 2.0 |
| Platforms | Linux on x86_64, arm64 and armhf; the documentation describes Linux hosts only |
| Download size | About 78 MB (x86_64 binary) |
| Minimum hardware | Server: 2 cores, 2 GB RAM. Agent: 1 core, 512 MB RAM |
| Default datastore | SQLite; embedded etcd, MySQL and PostgreSQL are also supported |
| Included components | containerd, Flannel, CoreDNS, Traefik ingress, ServiceLB, kube-router network policies, local-path-provisioner, Spegel image registry |
| Developer | K3s Project Authors (source on GitHub: k3s-io/k3s) |
| Official website | k3s.io; documentation at docs.k3s.io |
| Best for | Small clusters, edge and lab setups, CI and test clusters, Raspberry Pi class hardware |
Last verified: 14 November 2026, on the K3s GitHub releases and licence data and the home, quick-start and requirements pages of docs.k3s.io. Tested by us: Not tested yet.
What it does
- Runs a fully compliant Kubernetes control plane and node agent in a single process, and handles TLS certificates and most options through a simple launcher.
- Uses SQLite as the default datastore, so a single server needs no separate database; embedded etcd gives a high-availability setup with several servers.
- Installs kubectl, crictl and ctr, plus the
k3s-killall.shandk3s-uninstall.shscripts, and registers a service that restarts after a reboot or a crash. - Comes with Traefik as the ingress controller and ServiceLB as the load-balancer controller, so a small cluster can publish a service without extra software.
How to install K3s
One-node server
- Prepare a Linux machine with at least 2 cores and 2 GB of RAM, a unique hostname and an SSD if you can.
- Run the official install script:
curl -sfL https://get.k3s.io | sh - - Read the kubeconfig the installer writes to
/etc/rancher/k3s/k3s.yaml; the bundled kubectl uses it automatically.
Add an agent node
On the second machine set K3S_URL to the server address on port 6443 and K3S_TOKEN to the value stored on the server in /var/lib/rancher/k3s/server/node-token, then run the same install script. Setting K3S_URL makes the installer configure the node as an agent. If hostnames are not unique, give each node a name with K3S_NODE_NAME.
Network ports and firewall
The server needs port 6443 reachable from all nodes. Nodes talk to each other over UDP 8472 with the default Flannel VXLAN backend, and port 10250 is needed for the metrics server. Servers in an embedded-etcd high-availability setup also need 2379 and 2380 between them. The documentation warns not to expose the VXLAN port to the internet, and recommends turning off firewalld and ufw; if you keep them, it lists the rules to add for 6443 and the default pod and service ranges.
Requirements and distribution notes
- Architectures: x86_64, arm64 and armhf. K3s is expected to work on most modern Linux systems; the documentation adds notes for SUSE, Red Hat family, Ubuntu, Debian and Raspberry Pi OS.
- RHEL 10 needs the extra package
kernel-modules-extra. Releases before RHEL 8.4 carry a NetworkManager bug that needs nm-cloud-setup disabled. - Standard Raspberry Pi OS starts without cgroups; the documentation tells you to append
cgroup_memory=1 cgroup_enable=memoryto the boot command line. On ARM boards it recommends an external SSD, because etcd is write-intensive and SD cards and eMMC cannot cope. - Sizing guide: a server with 2 CPUs and 4 GB RAM is listed for up to 350 agent nodes; larger fleets need more CPU and RAM.
Who should use it, and who should not
A good fit: a sysadmin who wants a real Kubernetes API on one or a few small machines for testing, edge sites or a home lab, with the smallest possible install.
Not a fit: teams that need Windows server nodes, a vendor-supported platform with a support contract, or a graphical management layer out of the box. For deciding between K3s and full Kubernetes, read K3s vs Kubernetes. K3s clusters are often created with infrastructure code; see Terraform and Ansible vs Terraform, and find more tools in the DevOps and automation tools hub.
Limits and what we have not checked
- Not tested yet: we have not installed or run K3s v1.37.2+k3s1. The facts above come from the official GitHub data and documentation, checked on 14 November 2026.
- The install script downloads and runs software as root. Read it first at
https://get.k3s.ioor download the binary and its checksum file from the releases page instead. - Back up the datastore, and the token file before you rebuild a server. Plan upgrades: Kubernetes minor versions change behaviour, and the release notes list the changes.
- We did not verify the support status of individual older Kubernetes lines; check the project’s release notes for the version you plan to run.
FAQ
Is K3s free?
Yes. K3s is open source under the Apache 2.0 licence. You pay only for the machines you run it on.
What is the latest K3s version?
v1.37.2+k3s1, released on 3 November 2026 on the project’s GitHub releases page. The number before the plus sign is the Kubernetes version it is built from.
What are the K3s system requirements?
A server node needs at least 2 CPU cores and 2 GB of RAM; an agent node needs 1 core and 512 MB. The software supports x86_64, arm64 and armhf Linux, and an SSD is recommended for the datastore.
Does K3s run on Windows?
The official requirements describe Linux systems only, so plan on a Linux server or VM. If you work on Windows, run K3s in a Linux virtual machine or on a separate Linux machine.
How do I install K3s?
Run curl -sfL https://get.k3s.io | sh - on a Linux machine. The script installs the service, kubectl and helper scripts, and writes the kubeconfig to /etc/rancher/k3s/k3s.yaml.
Which ports does K3s use?
6443 on the server for the API, UDP 8472 between nodes for Flannel VXLAN, 10250 for the metrics server, and 2379 and 2380 between servers when you use embedded etcd for high availability.
Last checked against official sources: 14 November 2026 (developer website: k3s.io). Versions and licence terms change — confirm on the developer's site before deploying in production.




