+14
Daily
+87
Weekly
+239
Monthly
34,416
stars
2,775
forks
289
watchers
5,846
prs
7,854
issues
1,059
releases
README
K3s - Lightweight Kubernetes =============================================== Lightweight Kubernetes. Production ready, easy to install, half the memory, all in a binary less than 100 MB. Great for: Edge IoT CI Development ARM Embedding k8s Situations where a PhD in k8s clusterology is infeasible What is this? --- K3s is a fully conformant production-ready Kubernetes distribution with the following changes: 1. It is packaged as a single binary. 1. It adds support for sqlite3 as the default storage backend. Etcd3, MariaDB, MySQL, and Postgres are also supported. 1. It wraps Kubernetes and other components in a single, simple launcher. 1. It is secure by default with reasonable defaults for lightweight environments. 1. It has minimal to no OS dependencies (just a sane kernel and cgroup mounts needed). 1. It eliminates the need to expose a port on Kubernetes worker nodes for the kubelet API by exposing this API to the Kubernetes control plane nodes over a websocket tunnel. K3s bundles the following technologies together into a single cohesive distribution: Containerd & runc Flannel for CNI CoreDNS Metrics Server Traefik for ingress Klipper-lb as an embedded service load balancer provider Kube-router netpol controller for network policy Helm-controller to allow for CRD-driven deployment of helm manifests Kine as a datastore shim that allows etcd to be replaced with other databases Local-path-provisioner for provisioning volumes using local storage Host utilities such as iptables/nftables, ebtables, ethtool, & socat These technologies can be disabled or swapped out for technologies of your choice. Additionally, K3s simplifies Kubernetes operations by maintaining functionality for: Managing the TLS certificates of Kubernetes components Managing the connection between worker and server nodes Auto-deploying Kubernetes resources from local manifests in realtime as they are changed. Managing an embedded etcd cluster What's with the name? -------------------- We wanted an installation of Kubernetes that was half the size in terms of memory footprint. Kubernetes is a 10 letter word stylized as k8s. So something half as big as Kubernetes would be a 5 letter word stylized as K3s. A '3' is also an '8' cut in half vertically. There is neither a long-form of K3s nor official pronunciation. Is this a fork? --------------- No, it's a distribution. A fork implies continued divergence from the original. This is not K3s's goal or practice. K3s explicitly intends not to change any core Kubernetes functionality. We seek to remain as close to upstream Kubernetes as possible. However, we maintain a small set of patches (well under 1000 lines) important to K3s's use case and deployment model. We maintain patches for other components as well. When possible, we contribute these changes back to the upstream projects, for example, with SELinux support in containerd. This is a common practice amongst software distributions. K3s is
Top issues
#7151Add support for `riscv64` architecture65 comments · 2023-03-27#7451Support embedded NATS as alternate cluster option to etcd21 comments · 2023-05-08#2245Upstream or remove Kubernetes patches17 comments · 2020-09-14#10901[Windows] CoreDNS pod IP is not updated on Windows node16 comments · 2024-09-16#10295Flannel-external-ip is ignored in cloud environments?11 comments · 2024-06-05#9295[Windows] Make internode pod communication work in the Windows environment10 comments · 2024-01-25#14393nix-snapshotter: CreateContainer fails for nix:0 images in embedded containerd (containerd#12980)9 comments · 2026-07-11#12849Flannel nftables support9 comments · 2025-08-31
Discussions
#14969Restoring from a sqlite backup on a new host3 comments · 2026-11-06#14949Can an agent join a server by hostname (SNI) through an SNI-routing proxy? (k3k HCP use case)2 comments · 2026-11-03#14946Pods on different nodes can’t communicate after joining an agent node (flannel VXLAN default)2 comments · 2026-11-01#14930k3s servers and agents from one OpenTofu-style config, VMs included1 comments · 2026-10-29#14908Embedded etcd 3.5.26 to 3.6: supported K3s path with current upstream 3.5.32 prerequisite?1 comments · 2026-10-27#14894Unable to add the K3s Node - "unhealthy cluster"1 comments · 2026-10-22#14839What can lead to server/cred/passwd being "newer than datastore"?6 comments · 2026-10-20#14680how does this even works? you create issue and you give solution and a pr?4 comments · 2026-09-20
Latest release
v1.37.2+k3s1 v1.37.2+k3s1 2026-11-03This release updates Kubernetes to v1.37.2, and fixes a number of issues. For more details on what's new, see the Kubernetes release notes. Changes since v1.37.1+k3s1: Add gateway-api-crd to help (14727) Run snapshotrestore test entries in parallel (14733) Deps: bump containerd to v2.3.6 (14744) Bump Traefik to v3.7.14 and gateway-api to 1.6.2 (14757) Bump gateway-api to 1.6.3 (14769) Bump K3s-root version to v0.15.3 (14782) Bump flannel to v0.28.10 (14796) Bump containerd to v2.3.7 (14805) Update kube-roter to v2.11.1 (14762) Remove unused replace directives (1482