🏗️ Kairos factory - Streamline derivatives maintenance

[mudler]

This card is a follow-up for the pending items in : #116

As now the focus is not more to streamline derivatives creation (it is just needed to build a dockerfile!) we want now to make it easier to maintain with an ease out process. The design goals were outlined in #116 already, so this is just focusing on the remaining bits that are towards moving into reducing the friction on the parts that are very hardcoded to specific linux distributions.

• CRDs to serve netboot artifacts and deployment over lan ( https://github.com/kairos-io/osbuilder/tree/netboot ) with pixiecore #1913
• osbuilder should allow nodeSelector/affinity arguments for the builder deployments #455
• 🌱 Streamline grub settings #435
• 🌱 Proper support for openRC in the oem layouts #511
• There should be only one framework image with the logic for all distros #1896
• Dockefiles should separate the base image from the "build strategy" (aka flavor) #1898
• spike: patch release process #2726
• spike: Create a kairos "installer" #2968
• 🌱 Conformance tests #958

Design goals (copied from #116)

• Be able to create a derivative from a Dockerfile with standard container build tools (buildah, docker, etc.)
• Be able to create a derivative from a Kubernetes manifest CRD, using also artifacts from the Kairos factory in a "static", immutable way. Instead of running dynamic commands, we focus on statically creating high reproducible builds of images.
• Be able to create custom OS from Kairos core releases from the CRD and a dedicated CLI with additional customizations: such as kernel, packages, etc.
• Be able to create assets to boot the OS in different scenarios: raw disk images for cloud, ISOs for baremetal, disk images for embedded platforms, netboot artifacts for booting from network
• Be able to netboot seamlessly from network with zero-touch infrastructure configuration - plugging into the existing network with our CRDs.
• Be able to create your own Kairos factory artifacts
• Be able to SBOM, sign, and trace all the artifacts in SLSA compliant base images #92 and 🌱 SBOM #51

[mudler]

seems talos is doing something similar to what we have: https://www.talos.dev/v1.7/learn-more/image-factory/

[sdwilsh]

A nice to have for this would be for the k3s version to be able to be specified. There is an ARG for the earthly target today, but I couldn't figure out the format of it to actually be able to specify something that worked.