v1.12.0-beta.0 #12228
smira
announced in
Announcements
v1.12.0-beta.0
#12228
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Talos 1.12.0-beta.0 (2025-11-14)
Welcome to the v1.12.0-beta.0 release of Talos!
This is a pre-release of Talos
Please try out the release binaries and report any issues at
https://github.com/siderolabs/talos/issues.
New User Volume type - bind
New field in UserVolumeConfig -
volumeTypethat defaults topartition, but can be set todirectory.When set to
directory, provisioning and filesystem operations are skipped and a directory is created under/var/mnt/<name>.The
directorytype enables lightweight storage volumes backed by a host directory, instead of requiring a full block device partition.When
volumeType = "directory":/var/mnt/<metadata.name>;provisioning,filesystemandencryptionare prohibited.Note: this mode does not provide filesystem-level isolation and inherits the EPHEMERAL partition capacity limits.
It should not be used for workloads requiring predictable storage quotas.
Disk Encryption
Talos versions prior to v1.12 used the state of PCR 7 and signed policies locked to PCR 11 for TPM based disk encryption.
Talos now supports configuring which PCRs states are to be used for TPM based disk encryption via the
options.pcrsfield in the
tpmsection of the disk encryption configuration.If user doesn't specify any options Talos defaults to using PCR 7 for backwards compatibility with existing installations.
This change was made to improve compatibility with systems that may have varying states in PCR 7 due to UEFI Secure Boot configurations
and users may wish to disable locking to PCR 7 state entirely.
Signed PCR policies will still be bound to PCR 11.
The currently used PCR's can be seen with
talosctl get volumestatus <volume> -o yamlcommand.New User Volume type - disk
volumeTypein UserVolumeConfig can be set todisk.When set to
disk, a full block device is used for the volume.When
volumeType = "disk":minSize,maxSize,grow).Embedded Config
Talos Linux now supports embedding the machine configuration directly into the boot image.
etcd
etcd container image is now pulled from
registry.k8s.io/etcdinstead ofgcr.io/etcd-development/etcd.Ethernet Configuration
The Ethernet configuration now includes a
wakeOnLANfield to enable Wake-on-LAN (WOL) support.This field can be set to enable WOL and specify the desired WOL modes.
Extra Binaries
Talos Linux now ships with
nftbinary in the rootfs to support CNIs which shell out tonftcommand.Feature Lock
Talos now ignores the following machine configuration fields:
machine.features.rbac(locked to true)machine.features.apidCheckExtKeyUsage(locked to true)cluster.apiServer.disablePodSecurityPolicy(locked to false)These fields were removed from the default machine configuration schema in v1.12 and are now always set to the locked values above.
Talos force reboot
Talos now supports a "force" reboot mode, which allows skipping the graceful userland termination.
It can be used in situations where a userland service (e.g. the kubelet) gets stuck during graceful shutdown, causing the regular reboot flow to fail.
In addition,
talosctlwas updated to support this feature viatalosctl reboot --mode force.GRUB
Talos Linux introduces new machine configuration option
.machine.install.grubUseUKICmdlineto control whether GRUB should use the kernel command lineprovided by the boot assets (UKI) or to use the command line constructed by Talos itself (legacy behavior).
This option defaults to
truefor new installations, which means that GRUB will use the command line from the UKI, making it easier to customize kernel parameters via boot asset generation.For existing installations upgrading to v1.12, this option will default to
falseto preserve the legacy behavior.Kernel Module
Talos now supports optionally disabling kernel module signature verification by setting
module.sig_enforce=0kernel parameter.By default module signature verification is enabled (
module.sig_enforce=1).When using Factory or Imager supply as
-module.sig_enfore module.sig_enforce=0kernel parameters to disable module signature enforcement.Kernel Security Posture Profile (KSPP)
Talos now enables a stricter set of KSPP sysctl settings by default.
The list of overridden settings is available with
talosctl get kernelparamstatuscommand.Encrypted Volumes
Talos Linux now consistently provides mapped names for encrypted volumes in the format
/dev/mapper/luks2-<volume-id>.This change should not affect system or user volumes, but might allow easier identification of encrypted volumes,
and specifically for raw encrypted volumes.
Network Configuration
The network configuration under
.machine.network(with the exception of KubeSpan) has been deprecated, but it is still supported for backwards compatibility.New configuration documents were created to replace it, they will be documented in the future.
CRI Registry Configuration
The CRI registry configuration in v1apha1 legacy machine configuration under
.machine.registriesis now deprecated, but still supported for backwards compatibility.New configuration documents
RegistryMirrorConfig,RegistryAuthConfigandRegistryTLSConfigshould be used instead.talosctl image cache-serve
talosctlincludes new subcommandimage cache-serve.It allows serving the created OCI image registry over HTTP/HTTPS.
It is a read-only registry, meaning images cannot be pushed to it, but the backing storage can be updated by re-running the
cache-createcommand;Additionally
talosctl image cache-createhas some changes:--layout:oci(default),flat:ocipreserves current behavior;flatdoes not repack artifact layer, but moves it to a destination directory, allowing it to be served bytalosctl image cache-serve;--platform: now can accept multiple os/arch combinations:--platform=linux/amd64,linux/arm64);--platform=linux/amd64 --platform=linux/arm64);UEFI Boot
When using UEFI boot with systemd-boot as bootloader (on new installs of Talos from 1.10+ onwards), Talos will now not touch the UEFI boot order.
Talos 1.11 made a fix to create UEFI boot entry and set the boot order as first entry, but this behavior caused issues on some systems.
To avoid further issues, Talos will now only create the UEFI boot entry if it does not exist, but will not modify the boot order.
Component Updates
Linux: 6.17.7
Kubernetes: 1.35.0-alpha.3
CNI Plugins: 1.8.0
cryptsetup: 2.8.1
LVM2: 2_03_34
systemd-udevd: 257.8
runc: 1.3.2
CoreDNS: 1.13.1
etcd: 3.6.5
Flannel: 0.27.4
Flannel CNI plugin: v1.8.0-flannel2
runc: 1.3.3
containerd: 2.1.5
Talos is built with Go 1.25.4.
Contributors
Changes
291 commits
client.ErrEventNotSupportedlatesttag only on mainconstants.MinimumGOAMD64Levelusing build tag.gittext/templateinmachinedcode pathstalos.config.earlycommand line argChanges since v1.12.0-alpha.2
46 commits
client.ErrEventNotSupportedChanges from siderolabs/crypto
2 commits
Changes from siderolabs/gen
1 commit
Changes from siderolabs/go-api-signature
5 commits
invalid signatureerror when a signature is requiredChanges from siderolabs/go-debug
2 commits
Changes from siderolabs/go-kubernetes
1 commit
Changes from siderolabs/go-loadbalancer
1 commit
Changes from siderolabs/go-talos-support
2 commits
Changes from siderolabs/pkgs
55 commits
Changes from siderolabs/tools
20 commits
Dependency Changes
Previous release can be found at v1.11.0
Images
This discussion was created from the release v1.12.0-beta.0.
Beta Was this translation helpful? Give feedback.
All reactions