mnbro commented 5 days ago

Bake k0s as a systemd sysext image.

This PR aims to bake k0s as a systemd sysext and also provide a systemd unit file to manage k0s.

How to use

[ describe what reviewers need to do in order to validate this PR ]

Testing done

[Describe the testing you have done before submitting this PR. Please include both the commands you issued as well as the output you got.]

[ ] Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)
[ ] Inspected CI output for image differences: /boot and /usr size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.

mnbro commented 1 day ago

@tormath1 Can you please take a look and see if we can merge this?

After this is merged it would be nice to align k0s with the latest releases in the same way it was implemented for k3s in #98

mnbro commented 1 day ago

Thanks for the PR, some feedback:

do you want some units to be started when the sysext is loaded? If yes, you might need to add this kind of command: https://github.com/flatcar/sysext-bakery/blob/045a4f93a4b7c3668619edf9983d38c38467c730/create_containerd_sysext.sh#L69-L70

There will be no systemd units automatically enabled. As will be written in the documentation: i. choosing the embedded components of k0s will lead to some systemd units being enabled by the user(via Ignition) -> (k0s.service for controllers and k0sworker.service for workers )

ii. not opting for k0s embedded componets will lead to other systemd units being enabled by the user(via Ignition) ->(k0scontroller.service for controllers and k0sworker.service for workers)

could you write some documentation on how to use this sysext (e.g does it need provisioning with Ignition to create files / enable units / etc.)

Ok

mnbro commented 20 hours ago

@tormath1 I've committed the requested changes. Please take a look.

flatcar / sysext-bakery