k0sproject/k0s

k0s - The Zero Friction Kubernetes

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 44 minutes ago
Added to GitGenius on May 30th, 2026
Created on June 10th, 2020
Open Issues & Pull Requests: 223 (+0)
GitHub issues: Enabled
Number of forks: 524
Total Stargazers: 6,458 (+0)
Total Subscribers: 26 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 22.3 hours
Mean response time: 38.4 days
90th percentile: 71.0 days
Tracked items: 446

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 73% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "question" is answered fastest, typically in about 11 hours, while "area/configuration" waits about 5 days. 34% of tracked open issues have had no activity in three months. Only 4% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 115
New in 7 days: 12
Closed in 7 days: 4
Avg open age: 506 days
Stale 30+ days: 79
Stale 90+ days: 73

Recent activity

Opened in 7 days: 12
Closed in 7 days: 4
Comments in 7 days: 28
Events in 7 days: 57

Top labels

  • bug (202)
  • enhancement (149)
  • Stale (106)
  • documentation (32)
  • area/configuration (27)
  • question (23)
  • area/network (21)
  • good first issue (21)

Detailed Description

k0s is an open source Kubernetes distribution designed to minimize installation complexity and reduce developer friction. Distributed as a single binary with no host OS dependencies beyond the kernel, k0s enables users to bootstrap new clusters in minutes across any cloud, bare metal, edge, and IoT environments. The project is written in Go and maintains comprehensive documentation at docs.k0sproject.io.

The distribution is certified as 100% upstream Kubernetes and supports multiple installation methods including single-node, multi-node, airgap, and Docker-based deployments. k0s includes automatic lifecycle management through k0sctl, enabling straightforward cluster upgrades, backups, and restores. System requirements are modest, requiring only 1 vCPU and 1 GB RAM, making it suitable for resource-constrained environments. The project supports flexible deployment options with control plane isolation as the default configuration and scales from single-node setups to large high-availability clusters.

Key technical features include support for custom Container Network Interface plugins with Kube-Router as default and Calico as a preconfigured alternative. The distribution supports custom Container Runtime Interface plugins with containerd as the default runtime. Storage is flexible, supporting all Kubernetes storage options through Container Storage Interface implementations. Multiple datastore backends are available including etcd for multi-node clusters, SQLite for single-node deployments, and MySQL and PostgreSQL options. The project supports x86-64, ARM64, ARMv7, and RISC-V architectures and includes the Konnectivity service, CoreDNS, and Metrics Server.

The repository demonstrates active maintenance and community engagement.

k0s addresses a specific gap in Kubernetes deployment by providing a fully self-contained distribution that eliminates the separation between host OS and Kubernetes runtime. The project deliberately maintains a minimal philosophy, bundling only essential core components rather than packaging numerous opinionated add-ons. This design choice reduces maintenance burden and allows users to select their own solutions for ingresses, service meshes, and storage based on their specific requirements.

The project has been production-ready since version 1.21.0 and launched in November 2020. Building k0s from source requires GNU Make, POSIX shell, coreutils, findutils, and Docker, with all compilation performed inside Docker containers to eliminate the need for local Go installation. The build system supports multiple approaches including a self-contained method with statically linked binaries and a package maintainer method for environments without Docker. The project includes smoke testing capabilities and welcomes community contributions through its established contributing guide and code of conduct.