k3s-io/k3s

K3s is a lightweight, fully-featured Kubernetes distribution designed for edge, IoT, and resource-constrained environments. It provides a unified binary that manages the entire control plane and node agent lifecycle, including containerd, CNI, and etcd. The system supports advanced operational capabilities such as rootless execution, dual-stack networking, and automated certificate and secrets encryption management. It also includes robust tooling for cluster diagnostics, snapshotting, and integration with external networks like Tailscale.

This period focused on restructuring the K3s CLI into a multi-call binary and consolidating agent startup logic into platform-specific modules. The work involved removing legacy agent components, introducing rootless execution support, and updating dependencies to Kubernetes v1.36.3.

46 changes

This period focused on modernizing the codebase by introducing pluggable interfaces for managed clusters, etcd, and node configuration, while centralizing control-plane dependencies and proxy logic. Significant effort was also dedicated to expanding test coverage, adding integration and end-to-end tests for features like secrets encryption, certificate rotation, and dual-stack networking.

47 changes

This period focused on significantly expanding test coverage across Docker, E2E, and integration environments, while introducing new features for token management, VPN integration, and certificate monitoring. The codebase also saw architectural improvements, including centralized metrics, HTTPS handling, and structured logging, alongside a shift to Go-based test suites.

52 changes

This period focused on introducing local and remote etcd store abstractions to improve resilience during bootstrap and node restarts. The team also expanded test coverage by adding integration tests for the Nix snapshotter, large-scale cluster stability, and SELinux configuration across multiple Linux distributions.

6 changes

k3s-io/k3s was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.