/kairos

:penguin: :cyclone: Immutable, Cloud Native Linux meta-Distro built for Kubernetes, managed by Kubernetes

Primary LanguageGoApache License 2.0Apache-2.0




Kairos - Kubernetes-focused, Cloud Native Linux meta-distribution


Kubernetes-focused, Linux distribution - K3s - Automatic Node discovery/VPN


Kairos (formerly c3os) is an open-source project which brings Edge, cloud, and bare metal lifecycle OS management into the same design principles with a unified Cloud Native API.

At-a-glance:

  • :bowtie: Community Driven
  • :octocat: Open Source
  • 🔒 Linux immutable, meta-distribution
  • 🔑 Secure
  • 🐳 Container based
  • 🐧 Distribution agnostic

Kairos can be used to:

  • Easily spin-up a Kubernetes cluster, with the Linux distribution of your choice 🐧
  • Manage the cluster lifecycle with Kubernetes—from building, to provisioning, and upgrading 🚀
  • Create a multiple—node, single cluster that spans up across regions 🌍

For comprehensive docs, tutorials, and examples see our documentation.

Project status

  • Sep 15 2022: The project is undergoing a name rebranding from C3OS to Kairos. See rationale, and community poll here and the tracking issue. There could be disservices during the DNS transition, and we apologize. The documentation meanwhile, can be browsed in GitHub, inside the docs/content folder.

What is it ?

Kairos is a Cloud Native, meta-Linux distribution that can be built, managed, and ran with Kubernetes.

Why/when should I use it?

  • Build your Cloud on-premise, no vendor-lock in—completely Open Source
  • Brings the same convenience as a public cloud on—premises
  • Node provisioning, by bringing your image or using the Kairos releases.
  • For appliances that don't have to be Kubernetes application, specific-its design fits multiple use case scenarios

Features

  • At the current state, Kairos can create a multiple-node Kubernetes cluster with k3s—all k3s features are supported.
  • Upgrades can be done manually via CLI or with Kubernetes. Distribution of upgrades are done via container registries.
  • An immutable distribution that you can configure to your needs while maintaining its immutability.
  • Node configuration via a single, cloud-init config file.
  • Handle airgap upgrades with in—cluster, container registries.
  • Extend the image in runtime or build time via Kubernetes Native API.
  • Plans to support CAPI, with full device lifecycle management.
  • Plans to support up to RKE2, kubeadm, and much more!
  • Nodes can optionally connect autonomously via a fully meshed peer-to-peer (P2P) hybrid VPN network. It allows you to stretch a cluster up to 10000 km! Kairos can create private virtual network segments to enhance your cluster perimeter without any single point of failure (SPOF).

More than a Linux distribution

Kairos is available as ISO, qcow2, and NetBoot artifact for user convenience, but it is more than that. It allows turning any Linux distribution into a uniform, conformant distribution with an immutable design. As such, any distribution which is converted will share the same, common feature set between all of them, and they are managed in the same way by Kubernetes Native API components.

Any input OS will inherit:

  • Immutability
  • A/B upgrades
  • Booting mechanism fallback
  • Boot assessment
  • Single image, container-based atomic upgrades
  • Cloud-init support
  • All the Kairos feature-set

Kairos treats all the operating environments homogeneously in a distribution-agnostic fashion.

The OS is a container image. That means that upgrades to nodes are distributed via container registries.

Installations medium and other assets, required to boot bare metal or Edge devices, are built dynamically by the Kubernetes Native API components provided by Kairos.

livecd

Goals

The Kairos ultimate goal is to bridge the gap between Cloud and Edge by creating a smooth user experience. Several areas in the ecosystem can be improved for edge deployments to make it in pair with the cloud.

The Kairos project encompasses all the tools and architectural pieces needed to fill those gaps. This spans between providing Kubernetes Native API components to assemble OSes, deliver upgrades, and control nodes after deployment.

Kairos is distribution-agnostic and embraces openness: the user can provide their own underlying base image, and Kairos onboards it and takes it over to make it cloud-native, immutable, and plugs into an already rich ecosystem by leveraging containers as a distribution medium.

Contribute

Kairos is an open-source project, and any contribution is more than welcome! The project is big and narrows to various degrees of complexity and problem space. Feel free to join our chat, discuss in our forums and join us during Office hours.

We have an open roadmap, so you can always have a look at what's going on and actively contribute to it.

Useful links:

Community

You can find us at:

Project Office Hours

Project Office Hours is an opportunity for attendees to meet the maintainers of the project, learn more about the project, ask questions, and learn about new features and upcoming updates.

Office hours are happening weekly on Wednesday, 5:30 – 6:00 pm CEST (Central European Summer Time). Meeting link

Besides, we have monthly meetups to participate actively in the roadmap planning and presentation:

Roadmap planning

We will discuss agenda items and groom issues, where we plan where they fall into the release timeline.

Occurring: Monthly on the first Wednesday, 5:30 – 6:30 pm CEST. Meeting link

Roadmap presentation

We will discuss the items of the roadmaps and the expected features in the next releases.

Occurring: Monthly on the second Wednesday, 5:30 pm CEST [Meeting link

Alternatives

Other projects are similar to Kairos which are great and worth mentioning, and actually, Kairos took to some degree inspiration. However, Kairos has different goals and takes completely unique approaches to the underlying system, upgrade, and node lifecycle management.

Development

Building Kairos

Requirements: Needs only docker.

Run ./earthly.sh +all --FLAVOR=opensuse, which should produce a Docker image along with a working ISO.