bin: add flatcar-update tool for manual updates or airgapped updates#53
Merged
pothos merged 1 commit intoflatcar-masterfrom Dec 2, 2021
Merged
bin: add flatcar-update tool for manual updates or airgapped updates#53pothos merged 1 commit intoflatcar-masterfrom
pothos merged 1 commit intoflatcar-masterfrom
Conversation
tormath1
reviewed
Dec 2, 2021
pothos
force-pushed
the
kai/flatcar-update
branch
2 times, most recently
from
4de3016 to
8899bcb
Compare
While updates are managed through Nebraska, not every user wants to or can run their own service. Sometimes it would be more convenient if a local update command exists that also supports airgapped updates or helps a user to quickly jump between versions to reproduce an error. Add a flatcar-update tool (similar to flatcar-install) which users can run on the machine to force an update to a particular release or local update payload. On old machines this script can be fetched and executed, too, and should be CoreOS-compatible. Since update-engine does no version check, it's also possible to downgrade with the tool. The tool can disable updates after it ran, making it easy to do manual updates when no own Nebraska server exists.
pothos
force-pushed
the
kai/flatcar-update
branch
from
8899bcb to
e3084b6
Compare
tormath1
approved these changes
Dec 2, 2021
Contributor
tormath1
left a comment
tormath1
left a comment
There was a problem hiding this comment.
LGTM, thanks for this :)
pothos
added a commit
to flatcar-archive/coreos-overlay
that referenced
this pull request
Dec 2, 2021
This pulls in flatcar/init#53 to add the "flatcar-update" tool to the image, easing manual updates, rollbacks, channel/release jumping, and airgapped updates.
1 task
pothos
added a commit
to flatcar-archive/coreos-overlay
that referenced
this pull request
Dec 2, 2021
This pulls in flatcar/init#53 to add the "flatcar-update" tool to the image, easing manual updates, rollbacks, channel/release jumping, and airgapped updates.
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
2 participants
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.
While updates are managed through Nebraska, not every user wants to or
can run their own service. Sometimes it would be more convenient if a
local update command exists that also supports airgapped updates or
helps a user to quickly jump between versions to reproduce an error.
Add a flatcar-update tool (similar to flatcar-install) which users can
run on the machine to force an update to a particular release or local
update payload. On old machines this script can be fetched and
executed, too, and should be CoreOS-compatible. Since update-engine
does no version check, it's also possible to downgrade with the tool.
The tool can disable updates after it ran, making it easy to do manual
updates when no own Nebraska server exists.
Docs PR: flatcar-archive/flatcar-docs#191
How to use
See
./flatcar-update -h- depending on whether you run it from a dev image or a release image, set the force key option.Maybe consider to backport.
Testing done
A few test runs on a VM.
↓ will do in coreos-overlay
changelog/directory (user-facing change, bug fix, security fix, update)