matchbox VS netbootd

I also just came across Matchbox.

Software: * matchbox runs on one RPi for provisioning hardware * The remaining RPis and NUCs all run CoreOS * The matchbox server is responsible for deploying CoreOS to everything * Terraform deploys Kubernetes using Typhoon, 3 x masters (RPis) and 3 x workers (NUCs)

I have no idea why, but it's this, yes? https://matchbox.psdn.io/

There have been various different setups here. Have you looked at Matchbox?

> matchbox is a service that matches bare-metal machines to profiles that PXE boot and provision clusters. Machines are matched by labels like MAC or UUID during PXE and profiles specify a kernel/initrd, iPXE config, and Ignition config.

https://github.com/poseidon/matchbox

I wanted something that is almost zero-config, almost zero footprint (does not mirror packages, unpack ISOs, etc) to deploy on TORs and completely flexible in crafting preseed files, boot parameters, etc. The industry-grade Foreman makes it extremely difficult to iterate on crafting the perfect preseed mix in a shared-Foreman scenario, with its elaborate API model. I wanted a manifest that has-it-all. As an IaaC/Ansible user, I wanted to be able to ask netbootd to serve a given host (and stop serving it) on the fly, with a very simple API.