Relationship between bootc install and coreos-installer

[mitiemann]

Is there any plan to replace/base coreos-installer with/on bootc install?

My context: I plan to base an "embedded OS" on container technology. I have successfully prototyped a system, using coreos-installer to boot strap a bare metal install and then switching to my custom OS using bootc switch. I am now planning how to make this process easily repeatable for more bare metal installs on a small fleet of machines. Since coreos-installer uses ignition and bootc completely relies on container images, I'm wondering which route I should take for embedding/distributing secrets, and, hence, whether I should look more into how to do it with ignition or whether I should try to build isos/use bootc install --to-disk. But maybe I'm not thinking about this in the right way?

Any feedback welcome :-)

[cgwalters]

CoreOS is working to align increasingly with bootc. A related issue here is coreos/fedora-coreos-tracker#1906

I'm wondering which route I should take for embedding/distributing secrets,

Yes this is a complex topic. The big thing here is CoreOS tooling is historically not really designed to be forked - it's intended to be a "golden image" OS (and typically secrets come from remote ignition).

There's no one mechanism for secrets; in my experience it bifurcates heavily based on environment (bare metal, cloud and which particular cloud etc).