Releases: jeefy/booty
Releases · jeefy/booty
v0.3 🐳
Notable changes:
- Now supports iPXE booting
- Fedora CoreOS now a supported operating system 🎉
- Improved UI (and fixed VueJS router config so refresh/linking works)
- Experimental Support (in conjunction with custom butane configs) for installing/auto-rebasing to OSTree images (a la Universal Blue)
Full Changelog: v0.2...v0.3
v0.2 🦺
Notable changes:
- Fix: Updated references to pxelinux.0 (previous source removed)
- Allow users to click-and-view what a host's ignition file will render as
- Allow users to specify/override the default ignition.yaml per-host
Full Changelog: v0.1...v0.2
v0.1 - An actual release 🥾
When I started working on Booty, one of my long term goals was to allow machines to boot up and be put in a "holding pattern" if they weren't recognized. Since adding this, I think it's fitting to actually cut a release. So for this release, I'll just highlight the main function/goals of Booty:
- PXE boot into the latest Flatcar-Linux
- MAC address based hostnames
- Automatic conversion of Container Linux Config to Ignition JSON
- JSON "Hardware Database" (right now just a MAC-to-hostname mapping)
- Automatic updates retrieved from Flatcar-Linux
- Automatic drain/reboot of nodes (in conjunction with Kured)
- Web UI to add/edit/remove hosts
- Unrecognized MAC addresses go into the brig (boot loop till the MAC is registered)
Known Issues
- There is currently no way to "delete" an "Unknown Host" -- this should be acceptable since unknown hosts will simply boot-loop
- For the ARP lookup to work, Booty now requires
externalTrafficPolicy: Local
added to the Service (when run in Kubernetes) - Since it is now "stateful", when run in Kubernetes, Booty mounts a PVC to store the hardware database.
🥾 Happy Booting! 🥾