David Cassany Viladomat

Checked manually that failures show up in journal, I don't think we need explicit test for that.

> A better change would not use EfiSize for ARM since not all ARM systems boot via EFI. We probably need BootSize here Yes, probably we need a way to...

I don't think we need additional documentation for the time being as all keys are documented in yip project README and this properly linked in our docs in `Cloud-config` reference...

I think they both can stay. `git` is relaying on a well maintained library ([go-git](https://github.com/go-git/go-git)) and download is based on a small library ([grab](github.com/cavaliergopher/grab)) which does not depend on anything...

I believe all these are known issues related to https://github.com/rancher/rke2/issues/3888#issuecomment-1424699367 , in fact we are installing RKE2 from a tarball. We do not support RPM installation at runtime, as this...

Marking as blocked as currently there is no support for RKE2 when installed directly from the tarball, which is the procedure used within Elemental. In order to support RKE2 we...

Following Rancher conventions we could consider renaming the charts as: * elemental-operator-chart -> elemental * elemental-opertaor-crds-chart -> elemental-crd That way we would also align with marketplace charts.

> We already have the `SeedImage.spec.cloud-config` to be included in the system _after_ upgrade too, in order to add new configs. Indeed, `SeedImage.spec.cloud-config` is already executed at boot. However seedImage...

@dependabot rebase

* We need to include additional information in ManagedOSVersion resources: * Package list * Patches information * We need a process to collect the patches included in each build (I'd...