Additional entry in addition to active, fallback and recovery

[vipsharm]

Provide an option to enki with a cmdline (or a list) as input.

enki would generate then an extra entry/EFI file into the installer and the kairos system should have the entry installed in the system in addition to active, fallback and recovery .

Notes:

For Kairos reset flow, I need to add a single boot menu entry, with an additional cmdline "kairos.reset".

Adding it as extend cmdline loses the option to stay in recovery image, because it will always reset and reboot to active.
And, if i add it as generic cmdline that will create 6 EFIs into installed system 3 with default cmdline and 3 with this kairos.reset cmdline.

What we need is an option to add a cmdline for very specific usecase like reset, and have just one EFI instlled into the system alongwith active, fallback and recovery, This EFI will only be for this specific use case and we dont need fallback.recovery for this.

[Itxaka]

We should be able to provide this directly via conf file like we do with active/passive/recorey currently, no need for another entry:

Copy an extra conf for autoreset: kairos-io/kairos-agent#267
Return autoreset state for uki: kairos-io/kairos-sdk#74
Trigger autoreset service on autoreset state: kairos-io/packages#762
Set proper sentinel to autoreset: kairos-io/immucore#259

[Itxaka]

Everything merged.

Tested this manually.

• installed
• created some files under the persistent dirs
• restarted
• choose autoreset entry
• let it boot, it reset-ed and rebooted
• auto choose active on next boot
• files were no longer there on persistent

Will be in next patch release

[mudler]

reopening as we need still to tackle the changes in enki, however the autoreset entry is added

[mudler]

@Itxaka are you already working on the enki changes? I've just synced with Vipin and this is low prio atm

[Itxaka]

Nope, haven't touched this other than adding the autoreset @mudler

[jimmykarily]

What does loses the option to stay in recovery image, because it will always reset and reboot to active mean?

We currently have 2 flags:

• extend-cmdline -> adds the provides parameters to all the cmdlines (active, passive, recovery)
• extra-cmdline -> creates an additional entry for each one of active, passive, recovery with the provided parameters

If I understand correctly, we want an option that will only add the parameters to one specific entry? Or do we want an option that will create an additional entry (only one) with the provided parameters. If the latter is true, the efi file would have to be defined as well for the additional entry.

[ci-robbot]

I apologize for the confusion in my previous comment. You would like an option that adds the provided parameters to a single specific entry, specifically the "autoreset" entry, while still having the existing (active, passive, recovery) entries unchanged. In this case, an additional EFI file doesn't need to be defined for the additional entry, but the command line parameters should be set specifically for the "autoreset" entry when it is generated.

To summarize:

• Maintain existing (active, passive, recovery) entries unchanged
• Add the provided parameters to the "autoreset" entry only
• No need for a new EFI file for the "autoreset" entry

Please let me know if I've understood correctly.

[jimmykarily]

All merged now. Docs at the bottom of this page: https://kairos.io/docs/installation/trustedboot/ (will appear as soon as the docs site is built)