installer: verify extra disk filesystem support - #181
Merged
Conversation
Package the XFS and Btrfs formatting tools and retain Btrfs kernel support so every public extra-disk filesystem works in the installer and installed system. Share the supported-filesystem policy across validation and planning, and fail installer artifact generation when a formatter package is missing. Document the controlled mount paths and verified wipe semantics.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Packages XFS and Btrfs formatting support in the installer and exposes Btrfs alongside ext4 and XFS for managed extra disks.
The schema previously advertised XFS while the installer omitted its formatter, so a valid request could fail only after installation began. The filesystem allowlist is now shared across validation and planning, and installer artifact metadata generation fails when any supported formatter package is missing.
Operators can use ext4, XFS, or Btrfs at Katl-controlled /var/lib/katl/mnt/ paths with documented wipe and preservation semantics. The generated Kubernetes recipe revision is advanced because installer image inputs changed.