Skip to content

Releases: kairos-io/kairos

v3.1.0

10 Jul 12:40
@mauromorales mauromorales
v3.1.0
266565f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.1.0

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

Contributors

mauromorales, Itxaka, and 4 other contributors
Assets 501
Loading

v3.1.0-rc2

04 Jul 10:07
@Itxaka Itxaka
v3.1.0-rc2
93137fd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
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

Contributors

mauromorales, Itxaka, and renovate
Assets 497
Loading

v3.1.0-rc1

27 Jun 13:13
@jimmykarily jimmykarily
v3.1.0-rc1
d107406
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.1.0-rc1 Pre-release
Pre-release

What's Changed

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

Contributors

mauromorales, Itxaka, and 2 other contributors
Assets 501
Loading

v3.0.14

25 Jun 06:36
@mauromorales mauromorales
v3.0.14
8f9bb77
This commit was signed with the committer’s verified signature.
mauromorales Mauro Morales
GPG key ID: 0069994DD7392198
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.0.14

Security

  • 🔒 Rebuild of kcrypt-discovery-challenger and luet with newer Golang version to address CVE-2024-24790

Full Changelog: v3.0.13...v3.0.14

Assets 502
Loading

v3.1.0-alpha1

14 Jun 14:30
@mauromorales mauromorales
v3.1.0-alpha1
187efc6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.1.0-alpha1 Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: v3.0.4...v3.1.0-alpha1

Contributors

mauromorales, Itxaka, and 5 other contributors
Assets 503
Loading

v3.0.13

19 Jun 06:32
@mauromorales mauromorales
v3.0.13
eb23f05
This commit was signed with the committer’s verified signature.
mauromorales Mauro Morales
GPG key ID: 0069994DD7392198
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.0.13

⚠️ Known issues

Since v3.0.5 we introduced the 🐛 #2624 this is related to our backporting mechanism, which we will address starting in v3.1.x

🐛 Bug fixes

Full Changelog: v3.0.12...v3.0.13

Assets 502
Loading

v3.0.12

29 May 08:49
@mauromorales mauromorales
v3.0.12
de955b2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.0.12

⚠️ Known issues

Since v3.0.5 we introduced the 🐛 #2624 this is related to our backporting mechanism, which we will address starting in v3.1.x

What's Changed

Full Changelog: v3.0.11...v3.0.12

Contributors

mauromorales
Assets 500
Loading

v3.0.11

15 May 15:07
@mauromorales mauromorales
v3.0.11
c20862b
This commit was signed with the committer’s verified signature.
mauromorales Mauro Morales
GPG key ID: 0069994DD7392198
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.0.11

⚠️ Known issues

Since v3.0.5 we introduced the 🐛 #2624 this is related to our backporting mechanism, which we will address starting in v3.1.x

Full Changelog: v3.0.10...v3.0.11

Assets 497
Loading

v3.0.10

09 May 13:30
@Itxaka Itxaka
v3.0.10
5154c26
Compare
Choose a tag to compare
v3.0.10

⚠️ Known issues

Since v3.0.5 we introduced the 🐛 #2624 this is related to our backporting mechanism, which we will address starting in v3.1.x

Updated

  • Bumps framework to v2.7.32
  • Bumps kairos-agent to v2.8.14 (part of the framework)

Fixes

  • Prevent unwanted yaml fields to be marshalled: Fixes some step duplication when triggering the install via events like providers do
  • Avoid adding an extra line to os-release output: We were adding an extra line at the end of the os-release file, which some software had problems dealing with

Improvements

  • kairos-agent state will now show SecureBoot state of the node (on/off)
  • kairos-agent state will now show the common name of the EFI certificates in the node if any
  • kairos-agent state will now show a list of encrypted partitions by label and by device if any

image

Full Changelog: v3.0.9...v3.0.10

Assets 497
Loading

v3.0.9

02 May 15:16
@mauromorales mauromorales
v3.0.9
af1c888
This commit was signed with the committer’s verified signature.
mauromorales Mauro Morales
GPG key ID: 0069994DD7392198
Learn about vigilant mode.
Compare
Choose a tag to compare
v3.0.9

⚠️ Known issues

Since v3.0.5 we introduced the 🐛 #2624 this is related to our backporting mechanism, which we will address starting in v3.1.x

Fixes

Full Changelog: v3.0.8...v3.0.9

Contributors

mauromorales, kreeuwijk, and kaiehrhardt
Assets 498
Loading