chore(talos): bump to v1.14.1 and migrate machine config to multi-document format - #5720
Merged
Merged
Conversation
Bump TALOS_VERSION to v1.14.1 and update the schema reference to release-1.14. Move deprecated v1alpha1 fields (machine.sysctls, machine.files, cluster.apiServer, cluster.controllerManager, cluster.scheduler, cluster.proxy, cluster.coreDNS) to their dedicated multi-document config kinds (SysctlConfig, CRICustomizationConfig, EtcFileConfig, KubeAPIServerConfig, KubeAuditPolicyConfig, KubeControllerManagerConfig, KubeSchedulerConfig, KubeProxyConfig, KubeCoreDNSConfig) as recommended for Talos 1.14. cluster.secret/cluster.id and cluster.discovery are intentionally left on the deprecated fields for now, since their multi-document replacements (DiscoveryIdentityConfig/DiscoveryServiceConfig) change cluster identity/discovery semantics and warrant a separate, more careful migration on the live single-node cluster. Verified with `talosctl validate --strict` against the rendered config (Talos v1.14.1 client). Signed-off-by: Jordan Jones <git@svcs.ok8.sh>
Contributor
|
Note No rendered changes. konflate 0.6.4 · rendered |
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
TALOS_VERSIONfromv1.13.10tov1.14.1intalos/talos.env, and updates theyaml-language-serverschema comments intalos/machineconfig.yaml.j2fromrelease-1.12torelease-1.14.machine.sysctls→SysctlConfigmachine.files(CRI containerd snippet,/etc/nfsmount.conf) →CRICustomizationConfig+EtcFileConfigcluster.apiServer→KubeAPIServerConfig+KubeAuditPolicyConfig(audit policy is now a separate document kind;certSANsrenamed tocertExtraSANs)cluster.controllerManager→KubeControllerManagerConfigcluster.scheduler→KubeSchedulerConfigcluster.proxy.disabled→KubeProxyConfig.enabled: falsecluster.coreDNS.disabled→KubeCoreDNSConfig.enabled: falsecluster.secret/cluster.idandcluster.discoveryare intentionally left on the deprecated fields. Their replacements (DiscoveryIdentityConfig/DiscoveryServiceConfig) touch cluster identity and discovery-service registration on our only (single-node) production node, so migrating those deserves its own change and a more careful rollout rather than being bundled here. All old fields remain fully supported in 1.14, so nothing here is left in a broken state.talos/nodes/10.0.10.40.yamlandtalos/schematic.yaml.j2needed no changes — none of their fields are part of the deprecations in this release.Test plan
minijinja-cli --envusingtalos/talos.env+MACHINE_TYPE=controlplane.talosctl validate -m metal --strict(talosctl client v1.14.1) — passes clean with zero warnings (op:// secret refs swapped for placeholder base64 values for offline validation only, since real values come from 1Password at apply time viatask talos:apply-node).task talos:apply-node NODE=10.0.10.40and confirm the cluster comes back healthy (not run from here — leaving this for you to run against the real node).