sysext: Document OEM extensions and Flatcar extensions #319
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The use of systemd-sysext for OEM and Flatcar extensions was only documented in the release notes but not yet part of the docs. Add an overview about the systemd-sysext use in Flatcar and remove the Butane sysupdate config because the sysext-bakery is the better place to keep this up-to-date.
How to use
@jepio wanted to document the ZFS extension and I think it would make sense to cover the ZFS specifics with examples under https://www.flatcar.org/docs/latest/setup/storage/
Improvements and additions to the topic of Flatcar extension in general are welcome and would go into this PR, while we can make a new PR for ZFS examples in the storage docs pages.