Skip to content

feat(talos): roll v1.14.6 to the remaining nodes - #4949

Merged
dapperdivers merged 1 commit into
mainfrom
feat/talos-1.14.6-rollout
Nov 22, 2026
Merged

dapperdivers merged 1 commit into
mainfrom
feat/talos-1.14.6-rollout

Conversation

@dapperdivers

Copy link
Copy Markdown
Owner

Follow-up to #4948. The canary upgrade of talos-node-small-1 to v1.14.6 went through cleanly, so this removes the temporary nodeSelector and lets tuppr upgrade the other ten nodes, one at a time behind the existing health gates.

Canary checks:

  • Ready on v1.14.6 (kernel 6.18.63) about 3 minutes after the run started; all Talos services healthy.
  • UnattendedInstallStatus is installed with the v1.14.6 image, so the upgrade works with the install settings in UnattendedInstallConfig.
  • task talos:diff-node: no changes, so the node's config still matches the repo after the upgrade.
  • Runtime resources compared before and after: 19 of 21 types identical; the kubelet config and spec differ only in the static pod URL port, which is random per boot.
  • /var is 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.

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.
@dapperdivers
dapperdivers merged commit ac4961b into main Nov 22, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant