k0s - The Zero Friction Kubernetes by Team Lens

Help Shape the Future of k0s Kubernetes: Participate in our 2023 Users Survey

As we continue to strive towards making k0s the best Kubernetes distribution for you, we believe in the importance of listening to your experiences, feedback, and insights. That’s why we’ve rolled out the “k0s Kubernetes Users Survey 2023,” and we’re inviting you to share your thoughts! Read more at https://medium.com/k0sproject/help-shape-the-future-of-k0s-kubernetes-participate-in-our-2023-users-survey-9549d3a72e87. For the hasty ones, direct link to the survey is https://forms.gle/yNoVKJJYnUUyrqCR6.

What happened to Github stargazers?

In September 2022 we made a human error while creating some build automation scripts&tools for the repo. 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 ⭐ 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.

Overview

k0s is an 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.

k0s fits well in any cloud environment, but can also be used in IoT gateways, Edge and Bare metal deployments due to its simple design, flexible deployment options and modest system requirements.

Key Features

Different installation methods: single-node, multi-node, airgap and Docker
Automatic lifecycle management with k0sctl: upgrade, backup and restore
Modest system requirements (1 vCPU, 1 GB RAM)
Vanilla upstream Kubernetes (with no changes)
Available as a single binary with no external runtime dependencies besides the kernel
Flexible deployment options with control plane isolation as default
Scalable from a single node to large, high-available clusters
Supports custom Container Network Interface (CNI) plugins (Kube-Router is the default, Calico is offered as preconfigured alternative)
Supports custom Container Runtime Interface (CRI) plugins (containerd is the default)
Supports all Kubernetes storage options with Container Storage Interface (CSI)
Supports a variety of datastore backends: etcd (default for multi-node clusters), SQLite (default for single node clusters), MySQL, and PostgreSQL
Supports x86-64, ARM64 and ARMv7
Konnectivity service, CoreDNS, Metrics Server

Getting Started

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

Quick Start Guide - Create a full Kubernetes cluster with a single node that includes both the controller and the worker.
Install using k0sctl - Deploy and upgrade multi-node clusters with one command.
NanoDemo - Watch a .gif recording on how to create a k0s instance.
Run k0s in Docker - Run k0s controllers and workers in containers.
For docs, tutorials, and other k0s resources, see docs main page.

Join the Community

Lens Forums - Request for support and help from the Lens and k0s community.
GitHub Issues - Submit your issues and feature requests via GitHub.

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.

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.

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.

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:

Many of the addons such as ingresses, service meshes, storage etc. are VERY opinionated. We try to build this base with fewer opinions. :D
Keeping up with the upstream releases with many external addons is very maintenance heavy. Shipping with old versions does not make much sense either.

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.

Build

The requirements for building k0s from source are as follows:

GNU Make (v3.81 or newer)
coreutils
findutils
Docker

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

License

till/k0s-fork

ErrorLooks like something went wrong!

About

Resources

License

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Languages

Error
Looks like something went wrong!

Packages