📢 Kairos release v2.3.0

[mudler]

🗺 What's left for release

🎨 UX ( #773 )

• Custom partitioning #209

📖 Media/Blog posts ( #774 )
🤖 CAPI ( #120 )

🔒 CoCo/Security (#347)

• 🌱 openAMT #1113
• 🤖 Release testing UKI images with alphas #1150
• 📖 Create FIPS e2e examples for BYOI #362
• build framework-fips image #1539
• FIPS enabled Kairos flavors #361
• Create a test that boots UKI artifacts #1201

ARM:

• kairos-opensuse-leap-arm-rpi last working version was v1.6.1 #1435

🌱 Generic

• 🤖 Automate the release process more #1221

🐛 Bugfixing

• 🐛 Reset doesnt work on rpi #1486
• 🐛 resizefs on boot doesn't work #1448

⚙️ Maintenance

• Bump ubuntu images from 22.10 to 23.04 #1430

🔦 Highlights

✅ Release Checklist

• Stage 0 - Finishing Touches
  • Check kairos/packages, and for any needed update
  • Make sure CI tests are passing.
  • Consider cutting an rc, alpha, ... based on changes on the CI
• Stage 1 - Manual testing
  • How: Using the assets from master, make sure that test scenarios not covered by automatic tests are passing, and that docs are still aligned
    • Fedora flavor install, and manual upgrade works
    • ARM images (openSUSE, alpine) boots and manual upgrade works
• Stage 3 - Release
  • Tag the release on master.
• Stage 4 - Update provider-kairos
  • Update go mod to consume kairos-io/kairos.
  • Check if any changes on the pipelines and building pieces are required
    • Flavor changes
    • osbuilder version bumps
  • Update the CORE_VERSION file of kairos-io/provider to match the release tag of kairos-io/kairos
  • Tag the release on provider-kairos
• Stage 5 - Announcement
  • Add blog post for 2.3 release kairos-docs#52

[mauromorales]

Stage 1 QA results:

• Installed and manual upgrade works, however the newly installed os-release had contents for opensuse-leap and it was only after install that I saw the proper fedora ones
• ARM
  • openSUSE leap boots properly, manual upgrade errors with the following mesage: failed reading installation state: open /run/initramfs/cos-state/state.yaml: no such file or directory. Agent version 2.1.9
  • alpine (pending)

cc @mudler @Itxaka

[Itxaka]

Stage 1 QA results:

* ARM
  
  * openSUSE leap boots properly, manual upgrade errors with the following mesage: `failed reading installation state: open /run/initramfs/cos-state/state.yaml: no such file or directory`. Agent version 2.1.9

That its just a warning and its expected on arm. On install that file is created but of course, on arm there is no install so it cannot read that file. Still its an optional file for now..

[mauromorales]

@Itxaka ok makes sense, that it would be a warning, however it panics for me. Or is the "manual upgrade" supposed to be done in a different way on ARM?

[Itxaka]

@Itxaka ok makes sense, that it would be a warning, however it panics for me. Or is the "manual upgrade" supposed to be done in a different way on ARM?

In that case the issue is a different one, it should not have anything to do with the state.yaml 👍

[mauromorales]

Similar thing in Alpine

[mauromorales]

Opened #1593 because of the previously mentioned issue. Adding the blocked label

[mauromorales]

fixed now on master with the latest agent bump 667e671 doing new QA