Kairos release v3.2.1

[mudler]

🗺 What's left for release

• Use a different source for our os-release vars #2907
• Fix device json schema to allow other device paths #2906
• AuroraBoot doesn't copy cloud config file #2876
• 🐛 validate that kairos user is present #2875
• Error when draining pods with kubernetes upgrade #2866
• Identify system by other keys when installing grub #2895
• Examples showing #cloud-config files with stages.boot sections don't work #2892
• Dracut immucore should fatal if binaries are missing #2692

🔦 Highlights

This is a patch release

✅ Release Checklist

• Stage 0 - Finishing Touches
  • Check if Kairos-docs has any open PRs that need to be merged
  • Check if osbuilder is in the wanted version/latest
  • Check if k3s versions are correct (latest 3 versions should be available)
  • Check if any kairos/packages were bumped. Ensure they were merged and repo updated (Dependency Dashboard kairos-framework#2)
    • Cut a new release of the kairos-framework images
    • Bump the kairos-framework image in kairos
  • CI tests are passing
  • There are no critical CVEs in our internal components
  • 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
    • Generic hardware install
      • Manual upgrade
      • Interactive install
      • Manual recovery reset
      • Automatic reset
      • Provider decentralized test (like we used to run automatically)
    • RPi Standard Install (helps validate that partition expansion is working)
      • Manual upgrade
      • Passive booting
      • Recovery booting
      • Manual recovery reset
      • Automatic reset
      • /oem exists
      • k3s is running
    • Go through any of the known issues https://kairos.io/docs/
• Stage 3 - Release
  • Tag the release on master
  • Update the release with any known issues
• Stage 4 - Announcement
  • Merge docs updates for kairos and k3s version updates
  • Create a branch vX.Y.Z on the docs (not tagging), so the new release can be built and displayed on the menu. Ideally open a PR so we can review and add/remove some commits if needed (in case we have documented WIP which is not available on the given release)
  • Blog post announcement