We like to define kairos as a meta Linux Distribution as its goal is to convert any other distro to an immutable layout with Kubernetes Native components.
The Kairos stack is composed of the following:
Every component is extensible and modular such as it can be customized and replaced in the stack, and built off either locally or with Kubernetes
kairos node at first boot will start the
kairos-agent service, you can always check what’s happening by running
journalctl -fu kairos-agent.
This service will setup
edgevpn dynamically on first-boot, once it configures the machine it does not run on boot anymore, unless
/usr/local/.kairos/deployed is removed..
Those are the steps executed in sequence by the
edgevpn@kairosservice and enabled on start. The configuration for the connection is stored in
/etc/systemd/system.conf.d/edgevpn-kairos.envand depends on the cloud-init configuration file provided during installation time
k3s-agentservice. Configuration for each service is stored in
Kairos encompassess several components, some externally, most notably:
Elementaldocs applies to