🏭 Consolidate osbuilder and Auroraboot

[jimmykarily]

We currently have 2 different tools to build Kairos images:

• Auraboot, meant to be used outside Kubernetes
• osbuilder, meant to be used as a controller inside Kubernetes
  

Both of them have more responsibilities than building (e.g. Auroraboot handles netbooting, osbuilder handles upgrades) but they share the building part.

The current situation and the desired is described in the image above.

This is an epic to collect all the steps/issues toward the desired state.

• Osbuilder should use the Auroraboot image #1634
• Deprecate osbuilder-tools image in favor or Auroraboot #1635
• [TBD] Stop shelling out to scripts from Auroraboot and move all functionality to the Auroraboot binary

The last item needs to be discussed and it will be more clear when we have everything consolidated in one image.

[jimmykarily]

One more image describing the desired state of the various tools (osbuilder, auroraboot, enki) and the relations between them.

[jimmykarily]

We will soon be able to build Kairos container images using just Dockerfiles (no Earthly or other tools). There are 2 things missing to have the full "factory" experience:

• A tool that produces the various other artifacts from the container image (e.g. iso, img)
• A tool that wraps the whole flow in some nice UX

Right now the creation of additional artifacts happens in Earthly using osbuilder-tools image. Above we describe how Autoraboot should provide both the UX and the artifact building functionality. Let's consider splitting as such:

• enki is the tool that builds all types of artifacts given a container image
• Auroraboot is a cli interface that calls out to enki. It's meant to be used by humans.\
• Osbuilder controller also calls out to enki. It's meant to be used in Kubernetes in a declarative way.

The new suggestion above is that osbuilder doesn't use Auroraboot but enki directly. This allows us to focus the UX of Auroraboot to humans and not try to satisfy the needs of osbuilder too. enki should be able to cover both since it will be an internal tool, with no focus on UX.

[jimmykarily]

Work happening here:

• 1633 use enki as lib for build iso AuroraBoot#68
• Migrate to urfave cli v2 AuroraBoot#69