feat(talos)!: update to Talos 1.14 and topf 0.6.0 - #2372
Merged
Conversation
Talos 1.14 generates typed config documents and rejects the deprecated v1alpha1 fields the template patched, so every patch is rewritten to the new document kinds. Flannel and the PodSecurity admission document are removed with document-level deletes, control-plane scheduling is a taint delete on KubeNodeConfig, the install disk is a CEL selector that also matches by-id symlinks, and workload isolation is explicitly disabled to keep hostPID and host-mount workloads working. The ghcr.io/siderolabs/installer image is no longer published, so the talosVersion renovate annotation now tracks siderolabs/talos releases. talosctl-cluster-action v0.2 requires talosctl 1.14, so it is bumped too. Signed-off-by: Devin Buhl <devin@buhl.casa>
Signed-off-by: Devin Buhl <devin@buhl.casa>
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
1 participant
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.
Summary
topfto v0.6.0 andtalosctl/talosVersionto 1.14.0.machine.install,machine.kubelet,cluster.network,cluster.apiServer, ...), so every patch undertemplate/config/talosis rewritten to the new document kinds. Onlymachine.certSANs,machine.featuresandcluster.etcdremain v1alpha1.KubeFlannelCNIConfigandPodSecurityadmission documents are removed with document-level$patch: delete; control-plane scheduling is a taint delete onKubeNodeConfig.UnattendedInstallConfigCEL selector. Device paths also matchdisk.symlinks, so/dev/disk/by-id/...keeps working; serials usedisk.serial.FilesystemTrimConfig(the generator default, now explicit) andFilesystemScrubConfigfor XFS volumes.hostPID/ host-mount workloads (node-exporter, GPU plugins, in-tree iSCSI) and would silently switch on for existing users on their first 1.14 apply. The patch documents how to opt in.ghcr.io/siderolabs/installeris no longer published as of 1.14, which is why renovate never offered the update. ThetalosVersionannotation now trackssiderolabs/talosGitHub releases and the talos group matches that package only.home-operations/talosctl-cluster-actionbumped to v0.2.2; v0.2 requires talosctl 1.14. Supersedes feat(github-action)!: Update action home-operations/talosctl-cluster-action (v0.1.6 ➔ v0.2.1) - autoclosed #2333.Upgrade notes for existing clusters
A 1.13 node rejects the new documents, so run
just talos upgrade-node <node>beforejust talos apply-node <node>.kubernetesVersionstays at v1.36.4 (#2362 covers 1.37).Verification
just configure,oxfmt --check,just talos render,talosctl validate --mode metalwith topf 0.6.0 / talosctl 1.14.0.renovate-config-validatorandzizmorpass.