Skip to content

feat(talos): move machine configs to the v1.14 config contract - #4947

Merged
dapperdivers merged 2 commits into
mainfrom
feat/talos-config-contract-v1.14
Nov 21, 2026
Merged

dapperdivers merged 2 commits into
mainfrom
feat/talos-config-contract-v1.14

Conversation

@dapperdivers

Copy link
Copy Markdown
Owner

Phase 2 of the talhelper replacement (#4939): configContract goes from v1.13 to v1.14 and the patches become Talos 1.14 configuration documents. This is already live on all 11 nodes (applied 2026-11-21, no reboots); merging makes main match the cluster again.

The aim was no change in what the nodes do. A v1.14 base changes defaults as well as layout, so each one is pinned to what the cluster ran before.

Commits

  1. Config contract v1.14.
    • Patches and node files are now KubeAPIServerConfig, KubeAdmissionControlConfig, KubeAuthenticationConfig, KubeControllerManagerConfig, KubeSchedulerConfig, KubeletConfig, KubeNodeConfig, KubeNetworkConfig, ResolverConfig, SysctlConfig, TimeSyncConfig, KernelModuleConfig, KubeTalosAPIAccessConfig and UnattendedInstallConfig. etcd settings and machine.certSANs have no document yet and stay v1alpha1.
    • OIDC moves from machine.files + extraVolumes + --authentication-config to KubeAuthenticationConfig. Same two JWT authenticators; anonymous access stays off.
    • patches/global/70-pinned-defaults.yaml removes what a v1.14 base would turn on: workload isolation, the secure /var mount and the weekly filesystem trim. kube-proxy, CoreDNS and Flannel stay off.
    • startupProbes: false on the apiserver, as before. The probes are anonymous requests, so they must stay off while anonymous access is off.
    • render.sh appends the identity provider to KubeEtcdEncryptionConfig. Talos generated secretbox + identity before 1.14; the v1.14 base has secretbox only.
    • render.sh no longer injects the service-account key (the base carries it), and the doubled os:admin Talos API role is deduplicated.
  2. Diff tasks without values. talos:diff-node, diff-cluster and apply-node now print a summary (apply mode, line counts, changed keys and documents) instead of the raw diff, which contains CA keys and tokens. FULL=true shows the raw diff.

Not converted

patches/global/20-machine-files.yaml (containerd discard_unpacked_layers) is still machine.files, so Talos prints one deprecation warning. The CRICustomizationConfig replacement changes the merged containerd config header, which restarts containerd on every node. Planned for the next Talos upgrade.

Verified

  • Before applying, a checker built on the Talos 1.14.5 machinery compared each node's live config with the new render through the accessors the Talos controllers read: 70/70 settings identical on each control plane, 40/40 on each worker. CAs, tokens, the etcd encryption key and the service-account key are unchanged.
  • Applied one node at a time with --mode=no-reboot: one worker, then the three control planes, then the other workers. Runtime resources were snapshotted before and after each apply.
    • Workers: only the discovery endpoint label changed (legacy → default). kubelet and containerd did not restart.
    • Control planes: kube-apiserver restarted once each. etcd kept its leader and term.
  • On each control plane after apply: admin-cert login and OIDC login work, anonymous /livez and /version return 401, Secrets read back, a freshly minted service-account token is accepted, the rendered auth config has anonymous.enabled: false and both issuers, authorizers are Node and RBAC, the encryption config is secretbox then identity, and the pod has no probes.
  • task talos:diff-cluster: 11/11 no changes. 11/11 nodes Ready, all Flux Kustomizations and HelmReleases ready.
  • Encrypted pre-migration backups: .private/backups/2026-11-21-pre-config-contract-v1.14/ and Infisical /Infrastructure/Talos/Backups (TALOS_BACKUP_20261121_PREV114_*).

Set configContract to v1.14 and convert the patches to Talos 1.14
configuration documents. Node behaviour is unchanged: every default the
v1.14 base introduces is pinned to what the nodes ran under v1.13.

- patches and node files become KubeAPIServerConfig, KubeletConfig,
  KubeNodeConfig, ResolverConfig, SysctlConfig, TimeSyncConfig,
  UnattendedInstallConfig and friends; etcd, machine.certSANs and the
  containerd customization stay v1alpha1
- OIDC moves from machine.files + extraVolumes to KubeAuthenticationConfig,
  with anonymous access kept off and the apiserver probes kept off
- 70-pinned-defaults.yaml removes workload isolation, the secure EPHEMERAL
  mount and the weekly trim that the v1.14 base would turn on
- render.sh keeps the identity fallback provider in the etcd encryption
  config and no longer injects the service-account key (the base has it)
- the doubled os:admin Talos API role is deduplicated
A machine config diff contains CA keys and tokens, which made
talos:diff-node, diff-cluster and apply-node unsafe in logs and agent
sessions. diff.sh runs the dry run and prints only the apply mode, line
counts and the keys and documents that change. FULL=true shows the raw
diff.
@dapperdivers
dapperdivers merged commit 9da256f into main Nov 21, 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