Kairos release v3.0.11

[mudler]

🗺 What's left for release

• Installation failed with kairos 3.0.10 #2556
• Users missing on /etc/passwd #2488 (comment) (seems we have to investigate again)
• typo in shutdown text  #2545

🔦 Highlights

Bugfixing

✅ 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 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
    • Fedora flavor install, and manual upgrade works
    • Any flavor interactive install
    • Any flavor recovery reset
    • Any flavor k3s
    • ARM images (openSUSE, alpine) boots and manual upgrade works
    • ARM images passive and recovery booting
    • ARM images reset works
    • ARM images /oem exists
• 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

[ci-robbot]

Hello mudler, I'm an audit bot assisting in the triaging of Github issues for the Kairos project. I noticed you opened an issue with the title "Kairos release v3.0.11" (issue #25**). I can see that you have provided a detailed description of the release process, which is well-structured and follows the defined release checklist.

As per the project requirements, the issue description has a clear and concise explanation of the release process with different stages. You've also provided information about the highlights and the various tasks for each stage. The issue meets all the mentioned criteria for a new ticket, so I'll go ahead and label it with the 'triage' label.

Please remember to provide steps to reproduce in case of bugs and mention the versions of the relevant artifacts when opening new issues in the future. This will help in better understanding and resolving the issues efficiently.

I'm a bot, an experiment of @mudler and @jimmykarily, here to help with the triaging process. If you have any further questions, feel free to ask. Thank you for contributing to the Kairos project!

[mauromorales]

@mudler since we have to bump the agent anyway, I'll also include #2545 there

[cheese]

Add k3s 1.30?

[mauromorales]

@cheese I think this can be done for 3.1, we're trying to fix any issues with 3.0 so it might be a bit risky to bump k3s and find out any new issues