docs(nebraska): add multi-step updates guide #523
Draft
Conversation
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
- Add documentation for floor packages feature - Explain key concepts and update flow with examples - Document troubleshooting and common scenarios Signed-off-by: Ervin Rácz <ervin.racz@protonmail.com>
9 tasks
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://lemon-wave-085522403-523.westeurope.1.azurestaticapps.net |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add Multi-Step Updates documentation for Nebraska
This PR adds documentation for the multi-step updates (floor packages) feature. Should be merged together with the Nebraska release that includes this feature.
What are floor packages?
Floor packages are mandatory intermediate versions that Flatcar instances must install before proceeding to the final target version. This ensures safe update paths when breaking changes require instances to pass through specific versions (e.g., filesystem migrations, critical fixes).
Documentation covers: