-
Notifications
You must be signed in to change notification settings - Fork 36
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: implement the correct upgrade flow from 1.6.x to 1.7.x for SBC
Couple of things were missing: - schematic ID wasn't generated for empty extensions list, while we should also consider overlay which was detected for Talos < 1.7.x. - schematic change could be received a bit later than `TalosUpgradeController` starts the upgrade. That could lead to one unsuccessful attempt to upgrade as the wrong schematic id was used. Now schematic ID is generated when either extensions list is not empty, or overlay is not empty and if the node was joined to Omni running Talos < 1.7 and current Talos version is >= 1.7. Sync issues are handled by adding TalosVersion to the SchematicConfiguration: this way it is possible to make `TalosUpgradeController` wait until schematic configuration is synced to the Talos version it's going to upgrade to. Signed-off-by: Artem Chernyshev <[email protected]>
- Loading branch information
Showing
10 changed files
with
1,022 additions
and
846 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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