Repository navigation
feat(talos): roll v1.14.6 to the remaining nodes - #4949
Merged
Merged
Conversation
The canary (talos-node-small-1) upgraded cleanly: Ready on v1.14.6, its config still matches the repo, and its runtime resources are unchanged apart from the kubelet's per-boot static pod port. Remove the canary selector so tuppr upgrades the other ten nodes. The maintenance window stays held open until the run completes.
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
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.
Follow-up to #4948. The canary upgrade of
talos-node-small-1to v1.14.6 went through cleanly, so this removes the temporarynodeSelectorand lets tuppr upgrade the other ten nodes, one at a time behind the existing health gates.Canary checks:
UnattendedInstallStatusisinstalledwith the v1.14.6 image, so the upgrade works with the install settings inUnattendedInstallConfig.task talos:diff-node: no changes, so the node's config still matches the repo after the upgrade./varis still mounted without the secure option, as pinned.The maintenance window stays held open (
0 * * * */1h) for this supervised run. A last follow-up restores it to Sunday 02:00 / 6h.