Home

Awesome

k0s - The Zero Friction Kubernetes by Team Lens

<!-- When changing this file, consider to change docs/README.md, too! -->

Go build k0s network conformance Go Reference GitHub Repo stars Releases

GitHub release (latest by date) GitHub release (latest SemVer including pre-releases) GitHub commits since latest release (by date)

k0s-logo-dark k0s-logo-light

What happened to GitHub stargazers?

In September 2022 we made a human error while creating some build automation scripts&tools for the GitHub repository. Our automation accidentally changed the repo to a private one for few minutes. That itself is not a big deal and everything was restored quickly. But the nasty side effect is that it also removed all the stargazers at that point. :(

Before that mishap we had 4776 stargazers, making k0s one of the most popular Kubernetes distro out there.

So if you are reading this, and have not yet starred this repo we would highly appreciate the :star: to get our numbers closer to what they used to be.

The Repository

This repository ("k0s") is where Team Lens develops the k0s product together with the community. It is backed by a number of Kubernetes and cloud native ecosystem pioneers. This source code is available to everyone under the Apache License 2.0.

<!-- Start Overview -->

Overview

k0s is an open source, all-inclusive Kubernetes distribution, which is configured with all of the features needed to build a Kubernetes cluster and packaged as a single binary for ease of use. Due to its simple design, flexible deployment options and modest system requirements, k0s is well suited for

k0s drastically reduces the complexity of installing and running a CNCF certified Kubernetes distribution. With k0s new clusters can be bootstrapped in minutes and developer friction is reduced to zero. This allows anyone with no special skills or expertise in Kubernetes to easily get started.

k0s is distributed as a single binary with zero host OS dependencies besides the host OS kernel. It works with any Linux without additional software packages or configuration. Any security vulnerabilities or performance issues can be fixed directly in the k0s distribution that makes it extremely straightforward to keep the clusters up-to-date and secure.

<!-- End Overview --> <!-- Start Key Features -->

Key Features

<!-- End Key Features -->

Getting Started

If you'd like to try k0s, please jump in to our:

<!-- Start Join the Community -->

Join the Community

We welcome your help in building k0s! If you are interested, we invite you to check out the Contributing Guide and the Code of Conduct.

Community hours

We will be holding regular community hours. Everyone in the community is welcome to drop by and ask questions, talk about projects, and chat.

We currently have a monthly office hours call on the last Tuesday of the month.

To see the call details in your local timezone, check out https://dateful.com/eventlink/2735919704.

Adopters

k0s is used in numerous cases and environments. The range we've seen it being adopted ranges from very small far edge deployments to big data center deployments. Please add your use case to adopters list.

<!-- End Join the Community --> <!-- Start Motivation -->

Motivation

We have seen a gap between the host OS and Kubernetes that runs on top of it: How to ensure they work together as they are upgraded independent from each other? Who is responsible for vulnerabilities or performance issues originating from the host OS that affect the K8S on top?

→ k0s is fully self contained. It’s distributed as a single binary with no host OS deps besides the kernel. Any vulnerability or perf issues may be fixed in k0s Kubernetes.

We have seen K8S with partial FIPS security compliance: How to ensure security compliance for critical applications if only part of the system is FIPS compliant?

→ k0s core + all included host OS dependencies + components on top may be compiled and packaged as a 100% FIPS compliant distribution using a proper toolchain.

We have seen Kubernetes with cumbersome lifecycle management, high minimum system requirements, weird host OS and infra restrictions, and/or need to use different distros to meet different use cases.

→ k0s is designed to be lightweight at its core. It comes with a tool to automate cluster lifecycle management. It works on any host OS and infrastructure, and may be extended to work with any use cases such as edge, IoT, telco, public clouds, private data centers, and hybrid & hyper converged cloud applications without sacrificing the pure Kubernetes compliance or amazing developer experience.

<!-- End Motivation -->

Status

k0s is ready for production (starting from v1.21.0+k0s.0). Since the initial release of k0s back in November 2020, we have made numerous releases, improved stability, added new features, and most importantly, listened to our users and community in an effort to create the most modern Kubernetes product out there. The active development continues to make k0s even better.

<!-- Start Scope -->

Scope

While some Kubernetes distros package everything and the kitchen sink, k0s tries to minimize the amount of "add-ons" to bundle in. Instead, we aim to provide a robust and versatile "base" for running Kubernetes in various setups. Of course we will provide some ways to easily control and setup various "add-ons", but we will not bundle many of those into k0s itself. There are a couple of reasons why we think this is the correct way:

With strong enough arguments we might take in new addons, but in general those should be something that are essential for the "core" of k0s.

<!-- End Scope -->

Build

The requirements for building k0s from source are as follows:

All of the compilation steps are performed inside Docker containers, no installation of Go is required.

The k0s binary can be built in two different ways:

The "k0s" way, self-contained, all binaries compiled from source, statically linked and embedded:

make

The "package maintainer" way, without any embedded binaries (requires that the required binaries are provided separately at runtime):

make EMBEDDED_BINS_BUILDMODE=none

The embedded binaries can be built on their own:

make -C embedded-bins

Builds can be done in parallel:

make -j$(nproc)

Smoke test

Additionally to the requirements for building k0s, the smoke tests do require a local Go installation. you can run ./vars.sh go_version in a terminal to find out the version that's being used to build k0s. It will print the corresponding Go version to stdout.

To run a basic smoke test after build:

make check-basic