Skip to content

v3.2.2

Compare
Choose a tag to compare
@Itxaka Itxaka released this 12 Nov 15:15
· 71 commits to master since this release
a0c3578

Caution

We have identified a potential issue when upgrading from older versions into 3.2.2 via Kubernetes with suc-upgrade
If your upgrade scenario is via Kubernetes, we recommend NOT upgrading to this version and waiting for v3.2.3 which should be release between the 13th and 14th of November as a follow up to this release.
If you still need to upgrade, check #3010 for a workaround

✨ Improvements

  • Move kairos vars to their own file by @Itxaka in #2908
    • Now all the kairos vars are stored into /etc/kairos-release to not contaminate the system os-release
  • Add ubuntu 24.10 flavor by @mauromorales in #2930
    • Now you can enjoy the latest 24.10 ubuntu released in Kairos fashion
  • Build Ubuntu 24.04 Standard Image UKI on Github by @bencorrado in #2940
    • Now the released UKI base images provide a standard image that contains K3S for ease of consuming and generating Trusted Boot images.
  • Yip was updated across the system to version v1.11.0 which brings:
    • New trace level log output for extra logs
    • Move some logs from debug to trace to make debug logs clearer
    • Add missing name to stages that didnt have names for easy identification of the steps
    • Dont log empty command output
    • Do not duplicate errors when logging out
    • Nicer steps dump when running on debug
    • On failures print the source file for the errored step
  • Kairos-agent now allows installing a system with no users.
    • Can be enabled by setting the install.nousers to true
    • This will install a system with no users, thus blocked from sshing into it or login via physical methods
  • Kairos-agent now checks the system configurations to validate user+admin
    • At least one user needs to be added to the configs
    • At least one user needs to be in the admin group
    • Our configs set a Kairos user by default but this might change int he future and no users may be shipped by default, so we may consider the default kairos user bundled with our configs deprecated
    • This check can be skipped by the new setting install.nousers

⬆️ Dependencies

kairos-framewok was updated from v2.12.4 to v2.14.3 which brought the following updates (only showing updated packages):

Package Old version New version
suc-upgrade 0.2.3 0.3.0
kairos-overlay-files 1.1.58 1.5.1
immucore 0.5.1 0.6.0
kairos-agent 2.14.7 2.15.3

Notables changes in the packages:

  • suc-upgrade:
    • Will try to read the current release from /etc/kairos-release instead of /etc/os-release
  • immucore:
    • Dependency bumps, including yip from v1.10.0 to v1.11.0 which includes a nicer log output and mentioning the sources for stages on failures.
  • kairos-overlay-files:
    • Use /etc/kairos-release instead of /etc/os-release
    • Drop duplicated entries in defautl cmdlines
    • Drop duplicated filesystem expansion step
    • Pull datasources only during Install
  • kairos-agent:
    • Use /etc/kairos-release instead of /etc/os-release
    • Allow to install with no users by setting the install.nousers key to true in the config file. This allows to install a system with zero default users.
    • Validate that we have users in the config files and at least 1 is admin during install and upgrade to avoid installing/upgrading a system with no users and being locked out of the system. Can be override witht he above install.nousers key.
    • Read actual system configs during k8s upgrade. During k8s upgrade we were scanning the upgraded container for cloud config files, which skipped the actual system files.
    • Dependency bumps, including yip from v1.10.0 to v1.11.0 which includes a nicer log output and mentioning the sources for stages on failures.

New Contributors

Full Changelog: v3.2.1...v3.2.2