Skip to content

Releases: kairos-io/kairos

v3.2.1

07 Oct 08:11
Compare
Choose a tag to compare

What's Changed

✨ Improvements

  • Show sources in config string by @jimmykarily in kairos-io/kairos-agent#550
    • Now when checking the configs you will see the sources uses to generate them
  • Expose the Analize method of kairos-agent run-stage by @Itxaka in kairos-io/kairos-agent#548
    • now kairos-agent runstage can be run with the flag --analyze or -a to only show what steps would be run from a given stage and in the order they will be run.
  • Accept more paths to devices for install by @Itxaka in kairos-io/kairos-agent#552
    • Now the install target accepts devices identified by /dev/disk/by-{uuid,label,path,diskseq}

⬆️ Dependencies

🐛 Fixed bugs

🤖 CI related

Full Changelog: v3.2.0...v3.2.1

v3.2.1-rc1

04 Oct 13:46
0afe9dc
Compare
Choose a tag to compare
v3.2.1-rc1 Pre-release
Pre-release

What's Changed

Full Changelog: v3.2.0...v3.2.1-rc1

v3.2.0

30 Sep 14:09
9e0d3c8
Compare
Choose a tag to compare

This is a "milestone" release as is signifies the completeness of a set of planned stories. You can see what was planned for the v3.2.0 release in the relevant ticket: #2052

What's Changed

Full Changelog: v3.1.3...v3.2.0

v3.2.0-rc1

27 Sep 21:09
Compare
Choose a tag to compare
v3.2.0-rc1 Pre-release
Pre-release

See the v3.2.0 release notes - This was an rc

v3.1.3

16 Sep 14:32
b5ded86
Compare
Choose a tag to compare

Release highlights:

  • In the previous release, we introduced a fix for the broken permissions of the user's home directory. It turned out that the fix only applied to users created by the top level users: key in the Kairos configuration file. In this release, users created in various stages will also get their home directory permissions fixed. If for some reason, you don't want the script to recursively fix the home directory permissions, you can create a sentinel file to skip the fix and apply it on your own as you see fit.
  • Fixed an issue where we didn't calculate the upgrade image size and the always created an image with the default size (#2818)
  • Fixed an issue in Kairos upgrades through Kuberentes, where various host directories were also used in image size calculation (kairos-io/kairos-agent#537)
  • We now display the webui url below the QR code to avoid people having to plug a keyboard just to find the IP address of the node (#2826)
  • Fixed a bug in Alpine flavors where we passed the edgevpn arguments in the openrc service file wrongly (#2789)
  • Lots of version bumps on dependencies (mostly automated).

Known Issues

  • [Carry over from previous releases] RPi EFI booting no longer supported on kernels shipped with Ubuntu 24.04+ #2249

What's Changed

New Contributors

Full Changelog: v3.1.2...v3.1.3

v3.1.2

29 Aug 20:06
e0d89bc
Compare
Choose a tag to compare

⚠️ The following issues have been resolved, so it is safe to upgrade again:

Kairos user ids change on upgrade, breaking ssh login #2797
Long duration hang during boot #2802

What's Changed

  • 🤖 Check that install/recovery services are off during active boot by @Itxaka in #2775
  • 🐧 Disable pcrlock for all systemd distros by @Itxaka in #2778
  • 🐛 Empty machine-id instead of removing it by @Itxaka in #2784
  • 🐛 Fix +base-image for Remote Execution by @sdwilsh in #2808

Full Changelog: v3.1.1...v3.1.2

v3.1.2-rc1

29 Aug 07:35
Compare
Choose a tag to compare
v3.1.2-rc1 Pre-release
Pre-release

What's Changed

Full Changelog: v3.1.1...v3.1.2-rc1

v3.1.1

19 Jul 10:12
3e1b056
Compare
Choose a tag to compare

Upgrade issues

Be advised that there is currently an issue when upgrading from 3.0.x to 3.1.x in which the user ids will change. This will result in any files owned by the user under its /home directory to lose permissions which can lead to not being able to ssh (ssh keys will have a different user id)

We are currently working on a workaround, so you are advised to not upgrade until 3.1.2 is released with a fix for this.

What's Changed

Bug fixes 🐛

  • Disable make cache timer on fedora by @Itxaka in #2717
  • It's not possible to login on an Alpine 3.19 RPi fixed by @Itxaka #2439
  • Expired password on system with no rtc (e.g. rpi4) on Alpine fixed by @Itxaka #1994
  • cgroup_memory not mounted in Alpine rpi4 fixed by @Itxaka #2002
  • reset from the GRUB menu on alpine, gets stuck in an endless loop @Itxaka #2136

Known Issues

  • RPi EFI booting no longer supported on kernels shipped with Ubuntu 24.04+ #2249

Full Changelog: v3.1.0...v3.1.1

v3.1.0

10 Jul 12:40
266565f
Compare
Choose a tag to compare

Upgrade issues

Be advised that there is currently an issue when upgrading from 3.0.x to 3.1.x in which the user ids will change. This will result in any files owned by the user under its /home directory to lose permissions which can lead to not being able to ssh (ssh keys will have a different user id)

We are currently working on a workaround, so you are advised to not upgrade until 3.1.2 is released with a fix for this.

Potential Breaking Changes

By default, Uki artifacts (identified by the -uki suffix) no longer include Linux modules and firmware in the image. Real-world testing has shown that many EFI firmwares are very particular about the size of the EFI image, often refusing to boot if the file exceeds 300-400MB. Given the wide variety of EFI firmware implementations, predicting whether a UKI EFI file will boot on different hardware is challenging.

To enhance compatibility, we decided to slim down the UKI files by removing the largest components: the Linux modules and firmware packages. This results in EFI files around 200-300MB, which are much more likely to boot correctly across various EFI implementations.

However, this change comes with a trade-off. Smaller images, while being more compatible with a wide range of EFI firmwares, may lack comprehensive hardware support because they do not include all the Linux modules and firmware packages. This means that certain hardware components may not function correctly or optimally when using these slimmer UKI images.

On the other hand, larger UKI images, which include all necessary modules and firmware for extensive hardware support, provide better functionality and compatibility with a broad range of hardware. However, these larger images are more likely to encounter boot issues due to EFI firmware limitations, as many EFI implementations refuse to boot files larger than 300-400MB.

We publish -uki artifacts ourselves, which are the slimmed versions, as examples of how to build a slimmer UKI artifact. While these serve as a reference, we recommend always building your own custom images to tailor them to your specific hardware needs. If you need to include those packages for full hardware support, you can create a custom artifact to add them back, as detailed in the Kairos docs.

We recommend keeping your UKI EFI files as small as possible to maximize boot success across different EFI firmware implementations. While smaller images offer better compatibility, they may lack full hardware support. Conversely, larger images, which include all necessary modules and firmware, provide comprehensive hardware support but may fail to boot due to EFI firmware constraints.

Check out how to build your own base images with the Kairos Factory

What's Changed

💿 UKI

🐧

🐛

  • fix(nvidia): do not ship nohang in nvidia-arm builds by @mudler in #2433
  • Allow https protocol in ipxe by @jimmykarily in #2468
  • fix(orin): disable ISCSI in the initramfs generation by @mudler in #2474
  • 🐛 Move nfs-utils to common build target in opensuse flavor by @kaiehrhardt in #2495
  • 🐛 Install cryptsetup for all arches in opensuse by @Itxaka in #2691

📖

🔧

New Contributors

Full Changelog: v3.0.14...v3.1.0

v3.1.0-rc2

04 Jul 10:07
93137fd
Compare
Choose a tag to compare
v3.1.0-rc2 Pre-release
Pre-release

What's Changed

Full Changelog: v3.1.0-rc1...v3.1.0-rc2