System extensions do not run on the first boot after apply-config on a node about talos

[smira]

Make sure a few things as documented:

• if booting from ISO/PXE/..., Talos will install itself to the disk, and the installer being used should contain the extensions you need
• make sure your boot order is correct, that is you don't boot from an ISO after Talos was installed to the disk

Image Factory provides the links for all respective boot assets I mentioned above.

[nenkoru]

Make sure a few things as documented:

• if booting from ISO/PXE/..., Talos will install itself to the disk, and the installer being used should contain the extensions you need
• make sure your boot order is correct, that is you don't boot from an ISO after Talos was installed to the disk

Image Factory provides the links for all respective boot assets I mentioned above.

The boot order seems fine in proxmox.
Worth noting that I don't see the actual reboot happening with the selection of the A - Talos to choose after applying the controlplane.yaml config. Is this expected?

[nenkoru]

I am applying the controlplane.yaml as stated in the docs:
talosctl apply-config -f controlplane.yaml --insecure -n 192.168.10.10

[smira]

Please read my first answer. On initial install Talos does kexec correctly from install disk, but I guess when you do your hard reboot, it boots from something else.

[nenkoru]

Please read my first answer. On initial install Talos does kexec correctly from install disk, but I guess when you do your hard reboot, it boots from something else.

Alright, now it makes sense.
The installer installs the OS onto the disk, so the installer has to contain those extensions.
I just thought for a moment that all the system extensions are getting copied from the boot ISO to the install disk, but they do not.
They are getting installed by the installer. And they are included in the ISO's initramfs(?).
Closing the issue.

Oh yeah, and so once kexec is issued it was booting from the install disk, which was utilizing base installer which didn't contain those extensions. But once hard reboot was issued, the VM was booted from the ISO instead of the install disk(because the boot order was messed up).