Talos Linux is a modern Linux distribution built for Kubernetes.
MPL-2.0 License
Bot releases are visible (Hide)
Published by talos-bot over 2 years ago
Welcome to the v0.14.2 release of Talos!
Please try out the release binaries and report any issues at
https://github.com/talos-systems/talos/issues.
Talos is built with Go 1.17.7
Previous release can be found at v0.14.0
quay.io/coreos/flannel:v0.15.1
ghcr.io/talos-systems/install-cni:v0.7.0-2-gb4c9d21
docker.io/coredns/coredns:1.8.7
gcr.io/etcd-development/etcd:v3.5.1
k8s.gcr.io/kube-apiserver:v1.23.1
k8s.gcr.io/kube-controller-manager:v1.23.1
k8s.gcr.io/kube-scheduler:v1.23.1
k8s.gcr.io/kube-proxy:v1.23.1
ghcr.io/talos-systems/kubelet:v1.23.1
ghcr.io/talos-systems/installer:v0.14.2
k8s.gcr.io/pause:3.2
Published by talos-bot over 2 years ago
Welcome to the v0.15.0-alpha.2 release of Talos!
This is a pre-release of Talos
Please try out the release binaries and report any issues at
https://github.com/talos-systems/talos/issues.
talosctl apply/patch/edit
cli commands got revamped.
Separate flags --on-reboot
, --immediate
, --interactive
were replaced
with a single --mode
flag that can take the following values:
auto
new mode that automatically applies the configuration in immediate/reboot mode.no-reboot
force apply immediately, if not possible, then fail.reboot
force reboot with apply config.staged
write new machine configuration to STATE, but don't apply it (it will be applied after a reboot).interactive
starts interactive installer, only for apply
.Command talosctl gen config
now defaults to Kubernetes version pinning in the generate machine configuration.
Previously default was to omit explicit Kubernetes version, so Talos picked up the default version it was built against.
Old behavior can be achieved by specifiying empty flag value: --kubernetes-version=
.
Talos now preserves machine configuration as it was submitted to the node.
talosctl
commands which accept JSON patches (gen config
, cluster create
, patch machineconfig
) now support multiple patches, loading patches
from files with @file.json
syntax, and support loading from YAML format.
Talos now supports Oracle Cloud.
Platform network configuration was rewritten to avoid modifying Talos machine configuration.
Network configuration is performed independent of the machine configuration presence, so it works
even if Talos is booted in maintenance mode (without machine configuration is platform userdata).
Talos now supports Jetson Nano SBC.
Talos now accepts static pod definitions in the .machine.pods
key of the machine configuration.
Please note that static pod definitions are not validated by Talos.
Static pod definitions can be updated without a node reboot.
System extensions allow extending Talos root filesystem, which enables a set of different features, including custom
container runtimes, additional firmware, etc.
System extensions are only activated during Talos installation (or upgrade), and with system extensions installed, Talos
root filesystem is still immutable and read-only.
Please see extensions repository and documentation for more information.
Talos is built with Go 1.17.7
Added new kernel parameter talos.experimental.wipe=system
which can help resetting system disk for the machine
and start over with a fresh installation.
See Resetting a Machine on how to use it.
talosctl gen config
ip=
arg/lib/firmware
across initramfs and rootfskernel_param_spec
Modify call handlingapply
, edit
and patch
commandstalos.exp.wipe
kernel param to wipe system diskApplyDynamicConfig
list
, read
talosctl time
call in the teststalosctl get rd
talosctl upgrade-k8s
ip=
kernel argumenttalosctl gen config
ip=
arg/lib/firmware
across initramfs and rootfsnil
=m
kernel build optionsPrevious release can be found at v0.14.0
quay.io/coreos/flannel:v0.15.1
ghcr.io/talos-systems/install-cni:v0.8.0-alpha.0-2-g8f607fc
docker.io/coredns/coredns:1.8.7
gcr.io/etcd-development/etcd:v3.5.2
k8s.gcr.io/kube-apiserver:v1.23.3
k8s.gcr.io/kube-controller-manager:v1.23.3
k8s.gcr.io/kube-scheduler:v1.23.3
k8s.gcr.io/kube-proxy:v1.23.3
ghcr.io/talos-systems/kubelet:v1.23.3
ghcr.io/talos-systems/installer:v0.15.0-alpha.2
k8s.gcr.io/pause:3.2
Published by talos-bot over 2 years ago
Welcome to the v0.15.0-alpha.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/talos-systems/talos/issues.
talosctl apply/patch/edit
cli commands got revamped.
Separate flags --on-reboot
, --immediate
, --interactive
were replaced
with a single --mode
flag that can take the following values:
auto
new mode that automatically applies the configuration in immediate/reboot mode.no-reboot
force apply immediately, if not possible, then fail.reboot
force reboot with apply config.staged
write new machine configuration to STATE, but don't apply it (it will be applied after a reboot).interactive
starts interactive installer, only for apply
.Talos now preserves machine configuration as it was submitted to the node.
Talos now supports Oracle Cloud.
Platform network configuration was rewritten to avoid modifying Talos machine configuration.
Network configuration is performed independent of the machine configuration presence, so it works
even if Talos is booted in maintenance mode (without machine configuration is platform userdata).
Talos now supports Jetson Nano SBC.
Talos is built with Go 1.17.6
Added new kernel parameter talos.experimental.wipe=system
which can help resetting system disk for the machine
and start over with a fresh installation.
See Resetting a Machine on how to use it.
kernel_param_spec
Modify call handlingapply
, edit
and patch
commandstalos.exp.wipe
kernel param to wipe system diskApplyDynamicConfig
list
, read
talosctl time
call in the teststalosctl get rd
talosctl upgrade-k8s
ip=
kernel argumentkernel_param_spec
Modify call handlingapply
, edit
and patch
commandsnil
=m
kernel build optionsPrevious release can be found at v0.14.0
quay.io/coreos/flannel:v0.15.1
ghcr.io/talos-systems/install-cni:v0.8.0-alpha.0-1-g7c1f3cc
docker.io/coredns/coredns:1.8.7
gcr.io/etcd-development/etcd:v3.5.1
k8s.gcr.io/kube-apiserver:v1.23.2
k8s.gcr.io/kube-controller-manager:v1.23.2
k8s.gcr.io/kube-scheduler:v1.23.2
k8s.gcr.io/kube-proxy:v1.23.2
ghcr.io/talos-systems/kubelet:v1.23.2
ghcr.io/talos-systems/installer:v0.15.0-alpha.1
k8s.gcr.io/pause:3.2
Published by talos-bot almost 3 years ago
Welcome to the v0.14.1 release of Talos!
Please try out the release binaries and report any issues at
https://github.com/talos-systems/talos/issues.
Previous release can be found at v0.14.0
quay.io/coreos/flannel:v0.15.1
ghcr.io/talos-systems/install-cni:v0.7.0-1-gd6b73a7
docker.io/coredns/coredns:1.8.7
gcr.io/etcd-development/etcd:v3.5.1
k8s.gcr.io/kube-apiserver:v1.23.1
k8s.gcr.io/kube-controller-manager:v1.23.1
k8s.gcr.io/kube-scheduler:v1.23.1
k8s.gcr.io/kube-proxy:v1.23.1
ghcr.io/talos-systems/kubelet:v1.23.1
ghcr.io/talos-systems/installer:v0.14.1
k8s.gcr.io/pause:3.2
Published by talos-bot almost 3 years ago
Welcome to the v0.13.5 release of Talos!
Please try out the release binaries and report any issues at
https://github.com/talos-systems/talos/issues.
Previous release can be found at v0.13.4
quay.io/coreos/flannel:v0.13.0
ghcr.io/talos-systems/install-cni:v0.6.0
docker.io/coredns/coredns:1.8.4
gcr.io/etcd-development/etcd:v3.4.16
k8s.gcr.io/kube-apiserver:v1.22.3
k8s.gcr.io/kube-controller-manager:v1.22.3
k8s.gcr.io/kube-scheduler:v1.22.3
k8s.gcr.io/kube-proxy:v1.22.3
ghcr.io/talos-systems/kubelet:v1.22.3
ghcr.io/talos-systems/installer:v0.13.5
k8s.gcr.io/pause:3.2
Published by talos-bot almost 3 years ago
Welcome to the v0.15.0-alpha.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/talos-systems/talos/issues.
Talos now preserves machine configuration as it was submitted to the node.
There is some work still going on various cloud platforms to stop modifying machine configuration on the fly.
Added new kernel parameter talos.experimental.wipe=system
which can help resetting system disk for the machine
and start over with a fresh installation.
See Resetting a Machine on how to use it.
talos.exp.wipe
kernel param to wipe system diskApplyDynamicConfig
list
, read
talosctl time
call in the teststalosctl get rd
talosctl upgrade-k8s
ip=
kernel argumentnil
Previous release can be found at v0.14.0
quay.io/coreos/flannel:v0.15.1
ghcr.io/talos-systems/install-cni:v0.8.0-alpha.0
docker.io/coredns/coredns:1.8.6
gcr.io/etcd-development/etcd:v3.5.1
k8s.gcr.io/kube-apiserver:v1.23.1
k8s.gcr.io/kube-controller-manager:v1.23.1
k8s.gcr.io/kube-scheduler:v1.23.1
k8s.gcr.io/kube-proxy:v1.23.1
ghcr.io/talos-systems/kubelet:v1.23.1
ghcr.io/talos-systems/installer:v0.15.0-alpha.0
k8s.gcr.io/pause:3.2
Published by talos-bot almost 3 years ago
Welcome to the v0.14.0 release of Talos!
Please try out the release binaries and report any issues at
https://github.com/talos-systems/talos/issues.
When kexec support is disabled
Talos no longer drops Linux capabilities (CAP_SYS_BOOT
and CAP_SYS_MODULES
) for child processes.
That is helpful for advanced use-cases like Docker-in-Docker.
If you want to permanently disable kexec and capabilities dropping, pass kexec_load_disabled=1
argument to the kernel.
For example:
install:
extraKernelArgs:
- sysctl.kernel.kexec_load_disabled=1
Please note that capabilities are dropped before machine configuration is loaded,
so disabling kexec via machine.sysctls
will not be enough.
Cluster Discovery is enabled by default for Talos 0.14.
Cluster Discovery can be disabled with talosctl gen config --with-cluster-discovery=false
.
installer
and imager
imagesTalos supports two target architectures: amd64
and arm64
, so all Talos images are built for both amd64
and arm64
.
New image imager
was added which contains Talos assets for both architectures which allows to generate Talos disk images
cross-arch: e.g. generate Talos Raspberry PI disk image on amd64
machine.
As installer
image is used only to do initial install and upgrades, it now contains Talos assets for a specific architecture.
This reduces size of the installer
image leading to faster upgrades and less memory usage.
There are no user-visible changes except that now imager
container image should be used to produce Talos disk images.
Kubelet configuration can be updated without node restart (.machine.kubelet
section of machine configuration) with commands
talosctl edit mc --immediate
, talosctl apply-config --immediate
, talosctl patch mc --immediate
.
Kubelet service can now be restarted with talosctl service kubelet restart
.
Kubelet node IP configuration (.machine.kubelet.nodeIP.validSubnets
) can now include negative subnet matches (prefixed with !
).
Talos can now ship system logs
to the configured destination using either JSON-over-UDP or JSON-over-TCP:
see .machine.logging
machine configuration option.
Talos NTP sync process was improved to align better with kernel time adjustment periods and to filter out spikes.
A set of Talos ehancements is going to unlock a number of exciting features in the upcoming release of Sidero:
SideroLink
: a point-to-point Wireguard tunnel connecting Talos node back to the provisioning platform (Sidero).talos.event.sink=http://10.0.0.1:4000
) delivers Talos internal events to the specified destination.talos.logging.kernel=tcp://10.0.0.1:4001
) sends kernel logs as JSON lines over TCP or UDP.talosctl support
talosctl
CLI tool now has a new subcommand called support
, that can gather all
cluster information that could help with future debugging in a single run.
Output of the command is a zip
archive with all talos service logs, kubernetes pod logs and manifests,
talos resources manifests and so on.
Generated archive does not contain any secret information so it is safe to send it for analysis to a third party.
Talos is built with Go 1.17.5
talosctl upgrade-k8s
was improved to:
kubelet
to the version of the control plane components (without node reboot)So there is no need to update CoreDNS, Flannel container manually after running upgrade-k8s
anymore.
Talos now supports setting MTU and Virtual IPs on VLAN interfaces.
talosctl time
call in the teststalosctl get rd
talosctl upgrade-k8s
apply-config
work reliably in any Talos statekexec_file_load
talosctl support
command.machine.logging
upgrade-k8s
callaudit-policy-file
in kube-apiserver
static podtalosctl time
call in the teststalosctl get rd
Previous release can be found at v0.13.0
quay.io/coreos/flannel:v0.15.1
ghcr.io/talos-systems/install-cni:v0.7.0-1-gd6b73a7
docker.io/coredns/coredns:1.8.6
gcr.io/etcd-development/etcd:v3.5.1
k8s.gcr.io/kube-apiserver:v1.23.1
k8s.gcr.io/kube-controller-manager:v1.23.1
k8s.gcr.io/kube-scheduler:v1.23.1
k8s.gcr.io/kube-proxy:v1.23.1
ghcr.io/talos-systems/kubelet:v1.23.1
ghcr.io/talos-systems/installer:v0.14.0
k8s.gcr.io/pause:3.2
Published by talos-bot almost 3 years ago
Welcome to the v0.14.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/talos-systems/talos/issues.
When kexec support is disabled
Talos no longer drops Linux capabilities (CAP_SYS_BOOT
and CAP_SYS_MODULES
) for child processes.
That is helpful for advanced use-cases like Docker-in-Docker.
If you want to permanently disable kexec and capabilities dropping, pass kexec_load_disabled=1
argument to the kernel.
For example:
install:
extraKernelArgs:
- sysctl.kernel.kexec_load_disabled=1
Please note that capabilities are dropped before machine configuration is loaded,
so disabling kexec via machine.sysctls
will not be enough.
Cluster Discovery is enabled by default for Talos 0.14.
Cluster Discovery can be disabled with talosctl gen config --with-cluster-discovery=false
.
installer
and imager
imagesTalos supports two target architectures: amd64
and arm64
, so all Talos images are built for both amd64
and arm64
.
New image imager
was added which contains Talos assets for both architectures which allows to generate Talos disk images
cross-arch: e.g. generate Talos Raspberry PI disk image on amd64
machine.
As installer
image is used only to do initial install and upgrades, it now contains Talos assets for a specific architecture.
This reduces size of the installer
image leading to faster upgrades and less memory usage.
There are no user-visible changes except that now imager
container image should be used to produce Talos disk images.
Kubelet configuration can be updated without node restart (.machine.kubelet
section of machine configuration) with commands
talosctl edit mc --immediate
, talosctl apply-config --immediate
, talosctl patch mc --immediate
.
Kubelet service can now be restarted with talosctl service kubelet restart
.
Kubelet node IP configuration (.machine.kubelet.nodeIP.validSubnets
) can now include negative subnet matches (prefixed with !
).
Talos can now ship system logs
to the configured destination using either JSON-over-UDP or JSON-over-TCP:
see .machine.logging
machine configuration option.
Talos NTP sync process was improved to align better with kernel time adjustment periods and to filter out spikes.
A set of Talos ehancements is going to unlock a number of exciting features in the upcoming release of Sidero:
SideroLink
: a point-to-point Wireguard tunnel connecting Talos node back to the provisioning platform (Sidero).talos.event.sink=http://10.0.0.1:4000
) delivers Talos internal events to the specified destination.talos.logging.kernel=tcp://10.0.0.1:4001
) sends kernel logs as JSON lines over TCP or UDP.talosctl support
talosctl
CLI tool now has a new subcommand called support
, that can gather all
cluster information that could help with future debugging in a single run.
Output of the command is a zip
archive with all talos service logs, kubernetes pod logs and manifests,
talos resources manifests and so on.
Generated archive does not contain any secret information so it is safe to send it for analysis to a third party.
Talos is built with Go 1.17.5
talosctl upgrade-k8s
was improved to:
kubelet
to the version of the control plane components (without node reboot)So there is no need to update CoreDNS, Flannel container manually after running upgrade-k8s
anymore.
Talos now supports setting MTU and Virtual IPs on VLAN interfaces.
talosctl upgrade-k8s
apply-config
work reliably in any Talos statekexec_file_load
talosctl support
command.machine.logging
upgrade-k8s
callaudit-policy-file
in kube-apiserver
static podtalosctl upgrade-k8s
Previous release can be found at v0.13.0
quay.io/coreos/flannel:v0.15.1
ghcr.io/talos-systems/install-cni:v0.7.0-1-gd6b73a7
docker.io/coredns/coredns:1.8.6
gcr.io/etcd-development/etcd:v3.5.1
k8s.gcr.io/kube-apiserver:v1.23.0
k8s.gcr.io/kube-controller-manager:v1.23.0
k8s.gcr.io/kube-scheduler:v1.23.0
k8s.gcr.io/kube-proxy:v1.23.0
ghcr.io/talos-systems/kubelet:v1.23.0
ghcr.io/talos-systems/installer:v0.14.0-beta.1
k8s.gcr.io/pause:3.2
Published by talos-bot almost 3 years ago
Welcome to the v0.14.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/talos-systems/talos/issues.
When kexec support is disabled
Talos no longer drops Linux capabilities (CAP_SYS_BOOT
and CAP_SYS_MODULES
) for child processes.
That is helpful for advanced use-cases like Docker-in-Docker.
If you want to permanently disable kexec and capabilities dropping, pass kexec_load_disabled=1
argument to the kernel.
For example:
install:
extraKernelArgs:
- sysctl.kernel.kexec_load_disabled=1
Please note that capabilities are dropped before machine configuration is loaded,
so disabling kexec via machine.sysctls
will not be enough.
Cluster Discovery is enabled by default for Talos 0.14.
Cluster Discovery can be disabled with talosctl gen config --with-cluster-discovery=false
.
installer
and imager
imagesTalos supports two target architectures: amd64
and arm64
, so all Talos images are built for both amd64
and arm64
.
New image imager
was added which contains Talos assets for both architectures which allows to generate Talos disk images
cross-arch: e.g. generate Talos Raspberry PI disk image on amd64
machine.
As installer
image is used only to do initial install and upgrades, it now contains Talos assets for a specific architecture.
This reduces size of the installer
image leading to faster upgrades and less memory usage.
There are no user-visible changes except that now imager
container image should be used to produce Talos disk images.
Kubelet configuration can be updated without node restart (.machine.kubelet
section of machine configuration) with commands
talosctl edit mc --immediate
, talosctl apply-config --immediate
, talosctl patch mc --immediate
.
Kubelet service can now be restarted with talosctl service kubelet restart
.
Kubelet node IP configuration (.machine.kubelet.nodeIP.validSubnets
) can now include negative subnet matches (prefixed with !
).
Talos can now ship system logs
to the configured destination using either JSON-over-UDP or JSON-over-TCP:
see .machine.logging
machine configuration option.
Talos NTP sync process was improved to align better with kernel time adjustment periods and to filter out spikes.
A set of Talos ehancements is going to unlock a number of exciting features in the upcoming release of Sidero:
SideroLink
: a point-to-point Wireguard tunnel connecting Talos node back to the provisioning platform (Sidero).talos.event.sink=http://10.0.0.1:4000
) delivers Talos internal events to the specified destination.talos.logging.kernel=tcp://10.0.0.1:4001
) sends kernel logs as JSON lines over TCP or UDP.talosctl support
talosctl
CLI tool now has a new subcommand called support
, that can gather all
cluster information that could help with future debugging in a single run.
Output of the command is a zip
archive with all talos service logs, kubernetes pod logs and manifests,
talos resources manifests and so on.
Generated archive does not contain any secret information so it is safe to send it for analysis to a third party.
Talos is built with Go 1.17.4
talosctl upgrade-k8s
now syncs all Talos manifest resources generated from templates.
So there is no need to update CoreDNS, Flannel container manually after running upgrade-k8s
anymore.
Talos now supports setting MTU and Virtual IPs on VLAN interfaces.
apply-config
work reliably in any Talos statekexec_file_load
talosctl support
command.machine.logging
upgrade-k8s
callaudit-policy-file
in kube-apiserver
static podapply-config
work reliably in any Talos statePrevious release can be found at v0.13.0
quay.io/coreos/flannel:v0.15.1
ghcr.io/talos-systems/install-cni:v0.7.0
docker.io/coredns/coredns:1.8.6
gcr.io/etcd-development/etcd:v3.5.1
k8s.gcr.io/kube-apiserver:v1.23.0-rc.1
k8s.gcr.io/kube-controller-manager:v1.23.0-rc.1
k8s.gcr.io/kube-scheduler:v1.23.0-rc.1
k8s.gcr.io/kube-proxy:v1.23.0-rc.1
ghcr.io/talos-systems/kubelet:v1.23.0-rc.1
ghcr.io/talos-systems/installer:v0.14.0-beta.0
k8s.gcr.io/pause:3.2
Published by talos-bot almost 3 years ago
Welcome to the v0.14.0-alpha.2 release of Talos!
This is a pre-release of Talos
Please try out the release binaries and report any issues at
https://github.com/talos-systems/talos/issues.
When kexec support is disabled
Talos no longer drops Linux capabilities (CAP_SYS_BOOT
and CAP_SYS_MODULES
) for child processes.
That is helpful for advanced use-cases like Docker-in-Docker.
If you want to permanently disable kexec and capabilities dropping, pass kexec_load_disabled=1
argument to the kernel.
For example:
install:
extraKernelArgs:
- sysctl.kernel.kexec_load_disabled=1
Please note that capabilities are dropped before machine configuration is loaded,
so disabling kexec via machine.sysctls
will not be enough.
Cluster Discovery is enabled by default for Talos 0.14.
Cluster Discovery can be disabled with talosctl gen config --with-cluster-discovery=false
.
Kubelet service can now be restarted with talosctl service kubelet restart
.
Kubelet node IP configuration (.machine.kubelet.nodeIP.validSubnets
) can now include negative subnet matches (prefixed with !
).
Talos can now ship system logs
to the configured destination using either JSON-over-UDP or JSON-over-TCP:
see .machine.logging
machine configuration option.
Talos NTP sync process was improved to align better with kernel time adjustment periods and to filter out spikes.
A set of Talos ehancements is going to unlock a number of exciting features in the upcoming release of Sidero:
SideroLink
: a point-to-point Wireguard tunnel connecting Talos node back to the provisioning platform (Sidero).talos.event.sink=http://10.0.0.1:4000
) delivers Talos internal events to the specified destination.talos.logging.kernel=tcp://10.0.0.1:4001
) sends kernel logs as JSON lines over TCP or UDP.talosctl support
talosctl
CLI tool now has a new subcommand called support
, that can gather all
cluster information that could help with future debugging in a single run.
Output of the command is a zip
archive with all talos service logs, kubernetes pod logs and manifests,
talos resources manifests and so on.
Generated archive does not contain any secret information so it is safe to send it for analysis to a third party.
Talos is built with Go 1.17.3
talosctl upgrade-k8s
now syncs all Talos manifest resources generated from templates.
So there is no need to update CoreDNS, Flannel container manually after running upgrade-k8s
anymore.
kexec_file_load
talosctl support
command.machine.logging
upgrade-k8s
callaudit-policy-file
in kube-apiserver
static podkexec_file_load
Previous release can be found at v0.13.0
quay.io/coreos/flannel:v0.13.0
ghcr.io/talos-systems/install-cni:v0.7.0-alpha.0-1-g2bb2efc
docker.io/coredns/coredns:1.8.6
gcr.io/etcd-development/etcd:v3.5.1
k8s.gcr.io/kube-apiserver:v1.23.0-rc.0
k8s.gcr.io/kube-controller-manager:v1.23.0-rc.0
k8s.gcr.io/kube-scheduler:v1.23.0-rc.0
k8s.gcr.io/kube-proxy:v1.23.0-rc.0
ghcr.io/talos-systems/kubelet:v1.23.0-rc.0
ghcr.io/talos-systems/installer:v0.14.0-alpha.2
k8s.gcr.io/pause:3.2
Published by talos-bot almost 3 years ago
Welcome to the v0.13.4 release of Talos!
Please try out the release binaries and report any issues at
https://github.com/talos-systems/talos/issues.
kexec_file_load
Previous release can be found at v0.13.3
quay.io/coreos/flannel:v0.13.0
ghcr.io/talos-systems/install-cni:v0.6.0
docker.io/coredns/coredns:1.8.4
gcr.io/etcd-development/etcd:v3.4.16
k8s.gcr.io/kube-apiserver:v1.22.3
k8s.gcr.io/kube-controller-manager:v1.22.3
k8s.gcr.io/kube-scheduler:v1.22.3
k8s.gcr.io/kube-proxy:v1.22.3
ghcr.io/talos-systems/kubelet:v1.22.3
ghcr.io/talos-systems/installer:v0.13.4
k8s.gcr.io/pause:3.2
Published by talos-bot almost 3 years ago
Welcome to the v0.13.3 release of Talos!
Please try out the release binaries and report any issues at
https://github.com/talos-systems/talos/issues.
Kubelet service can now be restarted with talosctl service kubelet restart
.
Kubelet node IP configuration (.machine.kubelet.nodeIP.validSubnets
) can now include negative subnet matches (prefixed with !
).
Previous release can be found at v0.13.2
quay.io/coreos/flannel:v0.13.0
ghcr.io/talos-systems/install-cni:v0.6.0
docker.io/coredns/coredns:1.8.4
gcr.io/etcd-development/etcd:v3.4.16
k8s.gcr.io/kube-apiserver:v1.22.3
k8s.gcr.io/kube-controller-manager:v1.22.3
k8s.gcr.io/kube-scheduler:v1.22.3
k8s.gcr.io/kube-proxy:v1.22.3
ghcr.io/talos-systems/kubelet:v1.22.3
ghcr.io/talos-systems/installer:v0.13.3
k8s.gcr.io/pause:3.2
Published by talos-bot almost 3 years ago
Welcome to the v0.14.0-alpha.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/talos-systems/talos/issues.
When kexec support is disabled
Talos no longer drops Linux capabilities (CAP_SYS_BOOT
and CAP_SYS_MODULES
) for child processes.
That is helpful for advanced use-cases like Docker-in-Docker.
If you want to permanently disable kexec and capabilities dropping, pass kexec_load_disabled=1
argument to the kernel.
For example:
install:
extraKernelArgs:
- sysctl.kernel.kexec_load_disabled=1
Please note that capabilities are dropped before machine configuration is loaded,
so disabling kexec via machine.sysctls
will not be enough.
Cluster Discovery is enabled by default for Talos 0.14.
Cluster Discovery can be disabled with talosctl gen config --with-cluster-discovery=false
.
Kubelet service can now be restarted with talosctl service kubelet restart
.
Kubelet node IP configuration (.machine.kubelet.nodeIP.validSubnets
) can now include negative subnet matches (prefixed with !
).
Talos can now ship system logs to the configured destination using either JSON-over-UDP or JSON-over-TCP:
see .machine.logging
machine configuration option.
talosctl support
talosctl
CLI tool now has a new subcommand called support
, that can gather all
cluster information that could help with future debugging in a single run.
Output of the command is a zip
archive with all talos service logs, kubernetes pod logs and manifests,
talos resources manifests and so on.
Generated archive does not contain any secret information so it is safe to send it for analysis to a third party.
Talos is built with Go 1.17.2
talosctl upgrade-k8s
now syncs all Talos manifest resources generated from templates.
So there is no need to update CoreDNS, Flannel container manually after running upgrade-k8s
anymore.
talosctl support
command.machine.logging
upgrade-k8s
callaudit-policy-file
in kube-apiserver
static podtalosctl support
commandPrevious release can be found at v0.13.0
quay.io/coreos/flannel:v0.13.0
ghcr.io/talos-systems/install-cni:v0.7.0-alpha.0-1-g2bb2efc
docker.io/coredns/coredns:1.8.6
gcr.io/etcd-development/etcd:v3.5.1
k8s.gcr.io/kube-apiserver:v1.23.0-alpha.4
k8s.gcr.io/kube-controller-manager:v1.23.0-alpha.4
k8s.gcr.io/kube-scheduler:v1.23.0-alpha.4
k8s.gcr.io/kube-proxy:v1.23.0-alpha.4
ghcr.io/talos-systems/kubelet:v1.23.0-alpha.4
ghcr.io/talos-systems/installer:v0.14.0-alpha.1
k8s.gcr.io/pause:3.2
Welcome to the v0.13.2 release of Talos!
Please try out the release binaries and report any issues at
https://github.com/talos-systems/talos/issues.
When kexec support is disabled Talos no longer drops Linux capabilities (CAP_SYS_BOOT
and CAP_SYS_MODULES
) for child processes.
That is helpful for advanced use-cases like Docker-in-Docker.
If you want to permanently disable kexec and capabilities dropping, pass kexec_load_disabled=1
argument to the kernel.
For example:
install:
extraKernelArgs:
- kexec_load_disabled=1
Please note that capabilities are dropped before machine configuration is loaded,
so disabling kexec via machine.sysctls
(like in the section Reboots via kexec
) will not be enough.
Previous release can be found at v0.13.1
quay.io/coreos/flannel:v0.13.0
ghcr.io/talos-systems/install-cni:v0.6.0
docker.io/coredns/coredns:1.8.4
gcr.io/etcd-development/etcd:v3.4.16
k8s.gcr.io/kube-apiserver:v1.22.3
k8s.gcr.io/kube-controller-manager:v1.22.3
k8s.gcr.io/kube-scheduler:v1.22.3
k8s.gcr.io/kube-proxy:v1.22.3
ghcr.io/talos-systems/kubelet:v1.22.3
ghcr.io/talos-systems/installer:v0.13.2
k8s.gcr.io/pause:3.2
Published by talos-bot almost 3 years ago
Welcome to the v0.14.0-alpha.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/talos-systems/talos/issues.
When kexec support is disabled
Talos no longer drops Linux capabilities (CAP_SYS_BOOT
and CAP_SYS_MODULES
) for child processes.
That is helpful for advanced use-cases like Docker-in-Docker.
If you want to permanently disable kexec and capabilities dropping, pass kexec_load_disabled=1
argument to the kernel.
For example:
install:
extraKernelArgs:
- sysctl.kernel.kexec_load_disabled=1
Please note that capabilities are dropped before machine configuration is loaded,
so disabling kexec via machine.sysctls
will not be enough.
Cluster Discovery is enabled by default for Talos 0.14.
Cluster Discovery can be disabled with talosctl gen config --with-cluster-discovery=false
.
Talos can now ship system logs to the configured destination using either JSON-over-UDP or JSON-over-TCP:
see .machine.logging
machine configuration option.
Talos is built with Go 1.17.2
talosctl upgrade-k8s
now syncs all Talos manifest resources generated from templates.
So there is no need to update CoreDNS, Flannel container manually after running upgrade-k8s
anymore.
.machine.logging
upgrade-k8s
callaudit-policy-file
in kube-apiserver
static podPrevious release can be found at v0.13.0
quay.io/coreos/flannel:v0.13.0
ghcr.io/talos-systems/install-cni:v0.7.0-alpha.0
docker.io/coredns/coredns:1.8.6
gcr.io/etcd-development/etcd:v3.5.1
k8s.gcr.io/kube-apiserver:v1.23.0-alpha.3
k8s.gcr.io/kube-controller-manager:v1.23.0-alpha.3
k8s.gcr.io/kube-scheduler:v1.23.0-alpha.3
k8s.gcr.io/kube-proxy:v1.23.0-alpha.3
ghcr.io/talos-systems/kubelet:v1.23.0-alpha.3
ghcr.io/talos-systems/installer:v0.14.0-alpha.0
k8s.gcr.io/pause:3.2
Published by talos-bot almost 3 years ago
Welcome to the v0.13.1 release of Talos!
Please try out the release binaries and report any issues at
https://github.com/talos-systems/talos/issues.
When kexec support is disabled Talos no longer drops Linux capabilities (CAP_SYS_BOOT
and CAP_SYS_MODULES
) for child processes.
That is helpful for advanced use-cases like Docker-in-Docker.
If you want to permanently disable kexec and capabilities dropping, pass kexec_load_disabled=1
argument to the kernel.
For example:
install:
extraKernelArgs:
- sysctl.kernel.kexec_load_disabled=1
Please note that capabilities are dropped before machine configuration is loaded,
so disabling kexec via machine.sysctls
(like in the section Reboots via kexec
) will not be enough.
Previous release can be found at v0.13.0
quay.io/coreos/flannel:v0.13.0
ghcr.io/talos-systems/install-cni:v0.6.0
docker.io/coredns/coredns:1.8.4
gcr.io/etcd-development/etcd:v3.4.16
k8s.gcr.io/kube-apiserver:v1.22.2
k8s.gcr.io/kube-controller-manager:v1.22.2
k8s.gcr.io/kube-scheduler:v1.22.2
k8s.gcr.io/kube-proxy:v1.22.2
ghcr.io/talos-systems/kubelet:v1.22.2
ghcr.io/talos-systems/installer:v0.13.1
k8s.gcr.io/pause:3.2
Published by talos-bot about 3 years ago
Welcome to the v0.13.0 release of Talos!
Please try out the release binaries and report any issues at
https://github.com/talos-systems/talos/issues.
This release of Talos provides initial support for cluster membership discovery and KubeSpan.
These new features are not enabled by default, to enable them please make following changes to the machine configuration:
machine:
network:
kubespan:
enabled: true
cluster:
discovery:
enabled: true
Talos now reboots by default via kexec syscall which means BIOS POST process is skipped.
On bare-metal hardware BIOS POST process might take 10-15 minutes, so Talos reboots 10-15 minutes faster on bare-metal.
Kexec support can be disabled with the following change to the machine configuration:
machine:
sysctls:
kernel.kexec_load_disabled: "1"
Talos now natively supports four new cloud platforms:
Also generic cloud-init
nocloud
platform is supported in both networking and storage-based modes.
The address advertised by etcd can now be controlled with new machine configuration option machine.etcd.subnet
.
The addresses picked by kubelet can now be controlled with new machine configuration option machine.kubelet.nodeIP.validSubnets
.
CLI tool talosctl is now built for Windows and published as part of the release.
Linux: 5.10.69
Kubernetes: 1.22.2
containerd: 1.5.6
runc: 1.0.2
Talos is built with Go 1.17.1.
audit-policy-file
in kube-apiserver
static podAll
lookupAffiliate
structure (for the node)extraMounts
MountStatus
yaml:",inline"
tagaudit-policy-file
in kube-apiserver
static podAll
lookup methodPrevious release can be found at v0.12.0
quay.io/coreos/flannel:v0.13.0
ghcr.io/talos-systems/install-cni:v0.6.0
docker.io/coredns/coredns:1.8.4
gcr.io/etcd-development/etcd:v3.4.16
k8s.gcr.io/kube-apiserver:v1.22.2
k8s.gcr.io/kube-controller-manager:v1.22.2
k8s.gcr.io/kube-scheduler:v1.22.2
k8s.gcr.io/kube-proxy:v1.22.2
ghcr.io/talos-systems/kubelet:v1.22.2
ghcr.io/talos-systems/installer:v0.13.0
k8s.gcr.io/pause:3.2
Published by talos-bot about 3 years ago
Welcome to the v0.13.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/talos-systems/talos/issues.
Talos now natively supports four new cloud platforms:
Also generic cloud-init
nocloud
platform is supported in both networking and storage-based modes.
Linux: 5.10.69
Kubernetes: 1.22.2
containerd: 1.5.6
runc: 1.0.2
Talos is built with Go 1.17.1.
The address advertised by etcd can now be controlled with new machine configuration option machine.etcd.subnet
.
Talos now reboots by default via kexec syscall which means BIOS POST process is skipped.
On bare-metal hardware BIOS POST process might take 10-15 minutes, so Talos reboots 10-15 minutes faster on bare-metal.
Kexec support can be disabled with the following change to the machine configuration:
machine:
sysctls:
kernel.kexec_load_disabled: "1"
The addresses picked by kubelet can now be controlled with new machine configuration option machine.kubelet.nodeIP.validSubnets
.
This release of Talos provides initial support for cluster membership discovery and KubeSpan.
These new features are not enabled by default, to enable them please make following changes to the machine configuration:
machine:
network:
kubespan:
enabled: true
cluster:
discovery:
enabled: true
CLI tool talosctl is now built for Windows and published as part of the release.
All
lookupAffiliate
structure (for the node)extraMounts
MountStatus
yaml:",inline"
tagAll
lookup methodPrevious release can be found at v0.12.0
quay.io/coreos/flannel:v0.13.0
ghcr.io/talos-systems/install-cni:v0.6.0
docker.io/coredns/coredns:1.8.4
gcr.io/etcd-development/etcd:v3.4.16
k8s.gcr.io/kube-apiserver:v1.22.2
k8s.gcr.io/kube-controller-manager:v1.22.2
k8s.gcr.io/kube-scheduler:v1.22.2
k8s.gcr.io/kube-proxy:v1.22.2
ghcr.io/talos-systems/kubelet:v1.22.2
ghcr.io/talos-systems/installer:v0.13.0-beta.1
k8s.gcr.io/pause:3.2
Published by talos-bot about 3 years ago
Welcome to the v0.13.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/talos-systems/talos/issues.
Talos now natively supports four new cloud platforms:
Also generic cloud-init
nocloud
platform is supported in both networking and storage-based modes.
Linux: 5.10.69
Kubernetes: 1.22.2
containerd: 1.5.6
runc: 1.0.2
Talos is built with Go 1.17.1.
The address advertised by etcd can now be controlled with new machine configuration option machine.etcd.subnet
.
Talos now reboots by default via kexec syscall which means BIOS POST process is skipped.
On bare-metal hardware BIOS POST process might take 10-15 minutes, so Talos reboots 10-15 minutes faster on bare-metal.
Kexec support can be disabled with the following change to the machine configuration:
machine:
sysctls:
kernel.kexec_load_disabled: "1"
The addresses picked by kubelet can now be controlled with new machine configuration option machine.kubelet.nodeIP.validSubnets
.
This release of Talos provides initial support for cluster membership discovery and KubeSpan.
These new features are not enabled by default, to enable them please make following changes to the machine configuration:
machine:
network:
kubespan:
enabled: true
cluster:
discovery:
enabled: true
CLI tool talosctl is now built for Windows and published as part of the release.
All
lookupAffiliate
structure (for the node)extraMounts
MountStatus
yaml:",inline"
tagAll
lookup methodPrevious release can be found at v0.12.0
quay.io/coreos/flannel:v0.13.0
ghcr.io/talos-systems/install-cni:v0.6.0
docker.io/coredns/coredns:1.8.4
gcr.io/etcd-development/etcd:v3.4.16
k8s.gcr.io/kube-apiserver:v1.22.2
k8s.gcr.io/kube-controller-manager:v1.22.2
k8s.gcr.io/kube-scheduler:v1.22.2
k8s.gcr.io/kube-proxy:v1.22.2
ghcr.io/talos-systems/kubelet:v1.22.2
ghcr.io/talos-systems/installer:v0.13.0-beta.0
k8s.gcr.io/pause:3.2
Published by talos-bot about 3 years ago
Welcome to the v0.13.0-alpha.3 release of Talos!
This is a pre-release of Talos
Please try out the release binaries and report any issues at
https://github.com/talos-systems/talos/issues.
Talos now natively supports three new cloud platforms:
Also generic cloud-init
nocloud
platform is supported in both networking and storage-based modes.
The address advertised by etcd can now be controlled with new machine configuration option machine.etcd.subnet
.
Talos now reboots by default via kexec syscall which means BIOS POST process is skipped.
On bare-metal hardware BIOS POST process might take 10-15 minutes, so Talos reboots 10-15 minutes faster on bare-metal.
Kexec support can be disabled with the following change to the machine configuration:
machine:
sysctls:
kernel.kexec_load_disabled: "1"
This release of Talos provides initial support for cluster membership discovery and KubeSpan.
These new features are not enabled by default, to enable them please make following changes to the machine configuration:
machine:
network:
kubespan:
enabled: true
cluster:
discovery:
enabled: true
CLI tool talosctl is now built for Windows and published as part of the release.
All
lookupAffiliate
structure (for the node)extraMounts
MountStatus
yaml:",inline"
tagAll
lookup methodPrevious release can be found at v0.12.0
quay.io/coreos/flannel:v0.13.0
ghcr.io/talos-systems/install-cni:v0.6.0-alpha.0
docker.io/coredns/coredns:1.8.4
gcr.io/etcd-development/etcd:v3.4.16
k8s.gcr.io/kube-apiserver:v1.22.2
k8s.gcr.io/kube-controller-manager:v1.22.2
k8s.gcr.io/kube-scheduler:v1.22.2
k8s.gcr.io/kube-proxy:v1.22.2
ghcr.io/talos-systems/kubelet:v1.22.2
ghcr.io/talos-systems/installer:v0.13.0-alpha.3
k8s.gcr.io/pause:3.2