-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add assesment docs #323
base: main
Are you sure you want to change the base?
Add assesment docs #323
Conversation
Signed-off-by: Itxaka <[email protected]>
✅ Deploy Preview for kairos-io ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Itxaka <[email protected]>
Signed-off-by: Itxaka <[email protected]>
Co-authored-by: Ettore Di Giacinto <[email protected]>
Signed-off-by: Itxaka <[email protected]>
|
||
# Enabling Automatic Boot Assessment with Trusted Boot | ||
|
||
In this tutorial, we will walk through how to configure Kairos to enable **automatic boot assessment**, where the boot loader can determine the health of a boot entry. Specifically, we'll configure systemd services to trigger the `boot-complete.target` to mark boot entries as *good* or *bad*. We'll also cover how to implement automatic reboots when a service fails, allowing retries of a boot entry until success or exhaustion of attempts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By reading it entirely something is not really clear to me: here we say that the example is on how to enable the automatic boot assessment, but later we talk about marking an arbitrary service failure impacting the boot assessment - I think we should be explicit here in answering the following questions:
- what are system defaults ? is boot assessment enabled?
- is Kairos having a default boot assessment strategy?
- if Kairos does have a default , how it behaves, what are the limitations?
- If it doesn't, why we don't have a default for it?
- finally, how can we extend the boot assessment by including our own custom services to impact the system state check?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we currently dont have any assesment strategy...yet.
The idea was to write the docs first and then start enabling it ourselves, plus adding e2e tests for it.
Current boot assessment is set as the default, i.e. if multi-user.target is reached, then it considers the system as good and marks it as such.
But I get what you mean, I will redo this to extend to introduce first the current states of assesment on kairos and then keep this as how can be extended to support more things.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Expanded!
Co-authored-by: Ettore Di Giacinto <[email protected]>
Signed-off-by: Itxaka <[email protected]>
No description provided.