[RFE] Document built-in Systemd sysext images #1409
Assignees
Labels
Comments
github-project-automation
bot
moved this to 📝 Needs Triage
in Flatcar tactical, release planning, and roadmap
|
Great idea, we could also make this section more generalised about "extending the base OS system" (if only by header, for a start). The bakery also offers pre-baking images, we should cover this too: https://github.com/flatcar/sysext-bakery/?tab=readme-ov-file#baking-sysexts-into-flatcar-os-images |
pothos
added a commit
to flatcar/flatcar-website
that referenced
this issue
Apr 17, 2024
As discussed in flatcar/Flatcar#1409 the page on systemd-sysext images should also cover the customization of release images by putting extensions into the rootfs. Instead of having duplicate content that we need to keep up to date, add a reference to the systext-bakery README.
pothos
moved this from 📝 Needs Triage
to ✅ Testing / in Review
in Flatcar tactical, release planning, and roadmap
|
The new section on Flatcar release extensions: https://www.flatcar.org/docs/latest/provisioning/sysext/#flatcar-release-extensions |
github-project-automation
bot
moved this from ✅ Testing / in Review
to Implemented
in Flatcar tactical, release planning, and roadmap
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current situation
Currently, there is no documentation on how to use the built-in Sysext images except some Butane snippet or sharing configuration used in the CI.
Impact
It makes harder to discover the existing images and how to easily deploy them on Flatcar.
Ideal future situation
Supported extensions listed in the documentation + Butane / Ignition example to deploy it + a simple example to get started with the extension: if it takes some specific additional configuration, etc.
Implementation options
It could be under the "Provisioning Tools > Systemd sysext" section.
Additional information
n/a
The text was updated successfully, but these errors were encountered: