Talos Linux v1.14.0 released on 03-09-2026
Talos Linux v1.14.0 is out now. It matters because configuration is now modularised into repeatable multi-document kinds and the release brings major networking, storage and runtime changes that affect how clusters are configured and operated.
Read the full release notes and download binaries on the project GitHub: github.com/siderolabs/talos/releases/tag/v1.14.0
What’s in this release
- Multi-document configuration and Kubernetes modularisation — many monolithic v1alpha1 fields moved to dedicated kinds (examples: KubeAPIServerConfig, KubeNodeConfig, CRIBaseRuntimeSpecConfig, SysctlConfig, UdevRulesConfig, EtcFileConfig, ImageCacheConfig); new multi-doc documents take precedence when both formats coexist.
- Networking and DNS improvements — per-nameserver secure DNS (DoT/DoH) via ResolverConfig, DHCPv4 search-domain and ignoreRoutes support, HTTP probe support, and native BGP through embedded GoBGP with repeatable BGPInstanceConfig (VRF, ECMP/multipath, BFD caveat, route import selectors); Flannel now defaults to the nftables backend.
- Runtime and workload isolation changes — CRIBaseRuntimeSpecConfig and CRICustomizationConfig for CRI overrides, NRI enabled by default, and the runtime plane (CRI, kubelet, pods) can run in a sandbox namespace anchored by sandboxd (workloadIsolation controlled in SecurityProfileConfig).
Upgrade notes
- Many v1alpha1 monolithic fields are deprecated but still supported; migrate to the new multi-doc kinds where possible. Note mutual-exclusion rules (for example, .machine.baseRuntimeSpecOverrides is mutually exclusive with CRIBaseRuntimeSpecConfig) — configs containing both will be rejected.
- If you need to revert, remove the new multi-document config documents so the older v1alpha1 fields regain effect; also bear in mind workloadIsolation (newly generated configs default to true) breaks in-tree volume plugins that rely on host daemons — use CSI drivers for iSCSI and similar plugins.
Tell the team how it goes: report issues or share your experience on the GitHub issue tracker at github.com/siderolabs/talos/issues.
