You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Talos Linux now supports rotating the root CA certificate and key for Talos API and Kubernetes API.
Device Selectors
Talos Linux now supports physical: true qualifier for device selectors, it selects non-virtual network interfaces (i.e. en0 is selected, while bond0 is not).
DNS Caching
Talos Linux now provides a caching DNS resolver for host workloads (including host networking pods). It can be disabled with:
machine:
features:
hostDNS:
enabled: false
You can also enable dns caching for k8s pods with:
Please note that on running cluster you will have to kill CoreDNS pods for this change to apply.
Extension Services Config
Talos now supports supplying configuration files and environment variables for extension services.
The extension service configuration is a separate config document. An example is shown below:
Note: The use of environmentFile in extension service spec is now deprecated and will be removed in a future release of Talos.
Use ExtensionServiceConfig instead.
IPTables
Talos Linux now forces kubelet and kube-proxy to use iptables-nft instead of iptables-legacy (xtables) which was the default
before Talos 1.7.0.
Container images based on iptables-wrapper should work without changes, but if there was a direct call to legacy mode of iptables, make sure
to update to use iptables-nft.
Kubernetes Upgrade
The command talosctl upgrade-k8s now supports specifying custom image references for Kubernetes components via --*-image flags.
The default behavior is unchanged, and the flags are optional.
KubeSpan
Talos Linux disables by default a KubeSpan feature to harvest additional endpoints from KubeSpan members.
This feature turned out to be less helpful than expected and caused unnecessary performance issues.
Default NTP server was updated to be time.cloudflare.com instead of pool.ntp.org.
Default server is only used if the user does not specify any NTP servers in the configuration.
Talos Linux can now sync to PTP devices (e.g. provided by the hypervisor) skipping the network time servers.
In order to activate PTP sync, set machine.time.servers to the PTP device name (e.g. /dev/ptp0):
Talos Linux starting from this release uses RSA key for Kubernetes API Server Service Account instead of ECDSA key to provide better compatibility with external OpenID Connect implementations.
SBC
Talos has split the SBC's (Single Board Computers) into separate repositories.
There will not be any more SBC specific release assets as part of Talos release.
The default Talos Installer image will stop working for SBC's and will fail the upgrade, if used, starting from Talos v1.7.0.
The SBC's images and installers can be generated on the fly using Image Factory or using Imager for custom images.
The list of official SBC's images supported by Image Factory can be found in the Overlays repository.
Secure Boot Image
Talos Linux now provides a way to configure systemd-boot ISO 'secure-boot-enroll' option while generating a SecureBoot ISO image:
output:
kind: isoisoOptions:
sdBootEnrollKeys: force # default is still if-safeoutFormat: raw
Syslog
Talos Linux now starts a basic syslog receiver listening on /dev/log.
The receiver can mostly parse both RFC3164 and RFC5424 messages and writes them as JSON formatted message.
The logs can be viewed via talosctl logs syslogd.
This is mostly implemented for extension services that log to syslog.
Talos Linux now supports hardware watchdog timers configuration.
If enabled, and the machine becomes unresponsive, the hardware watchdog will reset the machine.
The watchdog can be enabled with the following configuration document:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Talos 1.7.0-beta.1 (2024-04-12)
Welcome to the v1.7.0-beta.1 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.
CA Rotation
Talos Linux now supports rotating the root CA certificate and key for Talos API and Kubernetes API.
Device Selectors
Talos Linux now supports
physical: true
qualifier for device selectors, it selects non-virtual network interfaces (i.e.en0
is selected, whilebond0
is not).DNS Caching
Talos Linux now provides a caching DNS resolver for host workloads (including host networking pods). It can be disabled with:
You can also enable dns caching for k8s pods with:
Please note that on running cluster you will have to kill CoreDNS pods for this change to apply.
Extension Services Config
Talos now supports supplying configuration files and environment variables for extension services.
The extension service configuration is a separate config document. An example is shown below:
For documentation, see Extension Services Config Files.
Note: The use of
environmentFile
in extension service spec is now deprecated and will be removed in a future release of Talos.Use
ExtensionServiceConfig
instead.IPTables
Talos Linux now forces
kubelet
andkube-proxy
to useiptables-nft
instead ofiptables-legacy
(xtables
) which was the defaultbefore Talos 1.7.0.
Container images based on
iptables-wrapper
should work without changes, but if there was a direct call tolegacy
mode ofiptables
, make sureto update to use
iptables-nft
.Kubernetes Upgrade
The command
talosctl upgrade-k8s
now supports specifying custom image references for Kubernetes components via--*-image
flags.The default behavior is unchanged, and the flags are optional.
KubeSpan
Talos Linux disables by default a KubeSpan feature to harvest additional endpoints from KubeSpan members.
This feature turned out to be less helpful than expected and caused unnecessary performance issues.
Previous behavior can be restored with:
Logging
Talos Linux now supports setting extra tags when sending logs in JSON format:
Time Sync
Default NTP server was updated to be
time.cloudflare.com
instead ofpool.ntp.org
.Default server is only used if the user does not specify any NTP servers in the configuration.
Talos Linux can now sync to PTP devices (e.g. provided by the hypervisor) skipping the network time servers.
In order to activate PTP sync, set
machine.time.servers
to the PTP device name (e.g./dev/ptp0
):OpenNebula
Talos Linux now supports OpenNebula platform.
Platforms
Talos Linux now supports Akamai Connected Cloud provider (platform
akamai
).Kubernetes API Server Service Account Key
Talos Linux starting from this release uses RSA key for Kubernetes API Server Service Account instead of ECDSA key to provide better compatibility with external OpenID Connect implementations.
SBC
Talos has split the SBC's (Single Board Computers) into separate repositories.
There will not be any more SBC specific release assets as part of Talos release.
The default Talos Installer image will stop working for SBC's and will fail the upgrade, if used, starting from Talos v1.7.0.
The SBC's images and installers can be generated on the fly using Image Factory or using Imager for custom images.
The list of official SBC's images supported by Image Factory can be found in the Overlays repository.
Secure Boot Image
Talos Linux now provides a way to configure systemd-boot ISO 'secure-boot-enroll' option while generating a SecureBoot ISO image:
Syslog
Talos Linux now starts a basic syslog receiver listening on
/dev/log
.The receiver can mostly parse both RFC3164 and RFC5424 messages and writes them as JSON formatted message.
The logs can be viewed via
talosctl logs syslogd
.This is mostly implemented for extension services that log to syslog.
Component Updates
Linux: 6.6.26
etcd: 3.5.11
Kubernetes: 1.30.0-rc.2
containerd: 1.7.15
runc: 1.1.12
Flannel: 0.24.4
Talos is built with Go 1.22.2.
Hardware Watchdog Timers
Talos Linux now supports hardware watchdog timers configuration.
If enabled, and the machine becomes unresponsive, the hardware watchdog will reset the machine.
The watchdog can be enabled with the following configuration document:
Contributors
Changes
227 commits
ExtraInfo
field for extensionssiderolink-launch
subcommandgo-talos-support
librarytalosctl upgrade-k8s
Install
for imager overlayslogs
command completionstalos_version_contract
for TF teststalosctl cluster create
DNSUpstreamController
environmentFile
for extensionsExtensionServicesConfig
DNSResolveCacheController
mptspi
drivertalosctl config new
talosctl gen secureboot
--nodes
talosctl disks
talosctl cluster create
actor id
to the SideroLink events sinkmerge.Merge
if map value is nilChanges since v1.7.0-beta.0
17 commits
Changes from siderolabs/crypto
3 commits
Changes from siderolabs/discovery-api
1 commit
Changes from siderolabs/discovery-client
3 commits
Changes from siderolabs/extras
6 commits
Changes from siderolabs/gen
1 commit
SyncMap
and bump stuffChanges from siderolabs/go-api-signature
21 commits
Changes from siderolabs/go-copy
2 commits
Changes from siderolabs/go-debug
1 commit
Changes from siderolabs/go-kmsg
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
PREEMPT_NONE
as recommended for serversChanges from siderolabs/siderolink
5 commits
agent
packageChanges from siderolabs/tools
17 commits
Dependency Changes
Previous release can be found at v1.6.0
Images
This discussion was created from the release v1.7.0-beta.1.
Beta Was this translation helpful? Give feedback.
All reactions