Skip to content
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

Ability to view and set efi boot order #2906

Closed
scheuk opened this issue Dec 5, 2020 · 3 comments
Closed

Ability to view and set efi boot order #2906

scheuk opened this issue Dec 5, 2020 · 3 comments
Assignees
Labels

Comments

@scheuk
Copy link

scheuk commented Dec 5, 2020

Feature Request

As an operator I would like the ability view and set the efi boot order via the talos api and exposed via the talosctl cli so that in an environment without ipmi, I can set the boot order to force the server to PXE boot.

Description

When you install an OS on a clean disk, the efi boot order is automatically switched to boot from the disk first even if the bios was configured for network boot first. In a traditionally linux OS you can change the boot order from the command line using efibootmgr post installation. By exposing this in the API we can have sidero force the node to pxe boot and wipe/and re-install talos into the disk.

@smira smira added this to the v0.8 milestone Dec 7, 2020
@smira smira self-assigned this Dec 7, 2020
@smira smira removed this from the v0.8 milestone Dec 7, 2020
@smira
Copy link
Member

smira commented Dec 7, 2020

This seems like something we could implement in Talos.

One way around right now might be to disable machine.install.bootloader in Talos config and enable server.pxeBootAlways in Sidero Server resource. This way Talos won't touch EFI boot manager and it will always PXE boot from Sidero. (not perfect, but workaround for now)

Copy link

github-actions bot commented Jul 4, 2024

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Jul 4, 2024
Copy link

This issue was closed because it has been stalled for 7 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 11, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants