Artem Chernyshev

The generated config for the machine may look like that: ```yaml --- version: v1alpha1 kind: InstallConfig spec: preserve: true disk: /dev/vda # immutable image: ghcr.io/siderolabs/installer:v1.2.0 extraKernelArgs: - ... extensions: -...

Update `go-yaml` to the latest version. Signed-off-by: Artem Chernyshev


Add ability to get pod logs right from the UI.

Otherwise to make `--wait=false` work you have to also pass `--with-init-node` flag, which looks weird. I guess it should be a nice change, unless it breaks some backward compability.

fix: use proper name for fetching existing extension configuration

1

The bug was leading to fetching `schematic-schematic-`, which is the incorrect name and it was always trying to create the resources instead of the update.

Can make the list item expandable and display failure reason in the details if the service is failing.

```mermaid flowchart TD BASE("Base Cloud Provider Support in Omni") CPLIB("Base Cloud Provider Library") QEMU("QEMU Cloud Provider") METAL("METAL Cloud Provider") TALEMU("Talemu Cloud Provider") KUBEVIRT("KubeVirt Cloud Provider") MC("Managed Control Planes") MP("Machine Pools...

- Read secureboot info from the node resources - Add `-secureboot` to the installer url when upgrading/installing Talos. - We might need to do special handling for preserving kernel params...