NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #305 by repository stars
Last release today
01 Oct 2026
Ships on a steady schedule
a new release about every 8 days
Some releases are documented
notes for 17 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
3045 releases · first in 2018
67464cbef fix: update the vulnerability dates and description
Welcome to the v1.14.0-rc.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/siderolabs/talos/issues.
Talos now supports DNS over TLS (DoT) and DNS over HTTPS (DoH) for secure DNS resolution.
These features allow Talos to encrypt DNS queries and responses, enhancing privacy and security for DNS traffic.
The DNS protocol can be configured on a per-name server basis in the ResolverConfig document, allowing for flexible configuration of DNS resolution.
The '--mode=reboot' option has been removed from the talosctl apply-config command; by default, configuration is applied without a reboot.
Most configuration changes don't require a reboot; the documentation lists the changes that do.
Talos now supports running native BGP routing instances on the host via embedded GoBGP servers, configured with BGPInstanceConfig documents.
This removes the need to ship FRR as a system extension for the common fabric-facing use case.
List of changes:
BGPInstanceConfig documents to configure local ASN, router-id, optional Linux VRF, advertised interfaces, neighbors, and per-route preferred source (routeSource).installRoutes: false to retain learned routes in the BGP RIB without installing them into the Linux routing table.importRoutes prefix selectors. Imports are one-way, preserve path attributes, and do not recursively import locally originated or previously imported paths.BGPPeerStatus resources (talosctl get bgppeerstatus).RouteSpec/RouteStatus now carry a multipath next-hop list to support ECMP and cross-family (RFC 8950) next-hops.Talos now supports mounting and provisioning btrfs filesystem for user volumes and existing volumes.
Support for btrfs is enabled by installing btrfs system extension.
Talos now supports overriding the default OCI runtime specification for CRI containers with a
CRIBaseRuntimeSpecConfig document:
apiVersion: v1alpha1
kind: CRIBaseRuntimeSpecConfig
overrides:
process:
rlimits:
- type: RLIMIT_NOFILE
hard: 1024
soft: 1024The .machine.baseRuntimeSpecOverrides field is deprecated and remains supported during the deprecation
period. It is mutually exclusive with CRIBaseRuntimeSpecConfig; configurations containing both are rejected.
Applying, updating, or removing either source regenerates the base runtime specification and restarts CRI
automatically. A machine reboot is no longer required.
Talos now supports customizing the CRI containerd configuration with named CRICustomizationConfig
documents. Each document contains a TOML fragment; fragments are merged in lexicographical order by name.
Applying, updating, or removing these documents updates the generated CRI configuration and restarts CRI
automatically.
The legacy /etc/cri/conf.d/20-customization.part machine-file configuration remains supported during the
deprecation period and is exposed under the reserved name customization. A CRICustomizationConfig document
cannot use that name.
NOTE: a machine reboot is no longer required to apply changes to CRI configuration.
Talos no longer disables NRI (Node Resource Interface) for the CRI containerd instance by default, so NRI is available
to use without any machine config patches.
To bring back the old behavior of NRI disabled by default, add the following machine configuration document:
apiVersion: v1alpha1
kind: CRICustomizationConfig
name: disable-nri
content: |
[plugins]
[plugins."io.containerd.nri.v1.nri"]
disable = trueThe default installer image has been updated to use the Image Factory.
The ghcr.io/siderolabs/installer image is no longer published with releases; use the Image Factory installer image instead.
DHCPv4 search domains are now applied to the resolver configuration.
DHCPv4 configuration now supports ignoreRoutes option to ignore routes provided by DHCPv4 servers.
Talos introduces support for configuring multiple discovery service endpoints.
Talos introduces new document for configuring the cluster discovery identity.
List of changes:
.cluster.discovery in the v1alpha1 config; use the DiscoveryServiceConfig document for discovery service configuration. The v1alpha1 config and DiscoveryServiceConfig are mutually exclusive..cluster.secret and cluster.id in the v1alpha1 config; use the DiscoveryIdentityConfig document for discovery identity configuration. The v1alpha1 config and DiscoveryIdentityConfig are mutually exclusive.base64.URLEncoding to base64.StdEncoding. This aligns the encoding with the rest of Talos.Volume encryption now supports an allowDiscards option (disabled by default) which passes TRIM/discard requests
through to the underlying device when the encrypted volume is opened.
This only enables passing discards through to the underlying device; Talos does not perform any fstrim/discard operation by itself.
Talos is now compatible with etcd v3.6.x only (the default etcd version was 3.6.x since Talos v1.11).
The default version is 3.7.0+ now.
etcd now serves its HTTP-only endpoints (/metrics, /health, the gRPC-gateway JSON API) on a dedicated
listener on port 2383, while the client port 2379 serves gRPC only. This keeps gRPC off Go's net/http
HTTP/2 server, avoiding watch-stream starvation under TLS (see etcd-io/etcd#15402, golang/go#58804,
etcd-io/etcd#21605).
Upgrade note: etcd metrics and the HTTP health endpoint are no longer reachable on 2379; scrape them on
port 2383 instead (same client mTLS as before). etcd gRPC clients and the Talos health check are unaffected.
Firewall might need to be adjusted to block the port 2383 if previously 2379 was blocked.
If --listen-metrics-urls was customized, the metrics should not move.
Talos now supports managing user-owned files under /etc with the new EtcFileConfig multi-document
configuration kind. The document name is the path relative to /etc, and each document owns the complete
file contents and mode.
This can be used to configure files such as /etc/nfsmount.conf or /etc/multipath.conf. Talos-managed
paths, including resolv.conf, hosts, machine-id, CRI and Kubernetes configuration, trust bundles, and
identity files, are rejected to prevent overriding files owned by Talos.
Talos can now periodically trim (the equivalent of the fstrim command) mounted filesystems which support trimming,
discarding unused blocks. This is useful for SSDs and thin-provisioned storage.
Trimming is opt-in via a new FilesystemTrimConfig document which sets the global trim interval:
apiVersion: v1alpha1
kind: FilesystemTrimConfig
interval: 168h0m0s # one weekThe default machine configuration for Talos 1.14+ includes a FilesystemTrimConfig document with a default trim interval of one week,
so trimming is enabled by default for eligible filesystems. For cluster which were upgraded from older versions, the FilesystemTrimConfig document will be missing,
so trimming will be disabled by default until the document is added.
When the document is present, Talos builds a stable schedule (hashed by node ID and volume ID, so trims are spread out
across volumes and across nodes in a cluster) and trims eligible volumes (ready disk/partition volumes with a
trim-capable filesystem; for encrypted volumes only when allowDiscards is set).
The trim interval can be overridden or disabled per-volume via a trim block on the volume documents
(VolumeConfig, UserVolumeConfig, ExistingVolumeConfig, ExternalVolumeConfig):
trim:
enabled: true
interval: 24h0m0sTalos now configures Flannel with the EnableNFTables option enabled, which uses nftables native backend instead of iptables-nft compatibility layer.
Talos no longer provisions the deprecated FlexVolume executable host path at
/usr/libexec/kubernetes. FlexVolume has been deprecated since Kubernetes 1.23.
Modern CSI plugin paths under /var/lib/kubelet are unaffected.
HostDNS configuration was moved from the v1alpha1 config .machine.features.hostDNS field to the new hostDNS in the ResolverConfig document.
Talos now supports HTTP network probes, allowing for monitoring of HTTP endpoints.
HTTP responses with status 200-399 are considered successful, while connection and transport errors are treated as failures.
Talos now supports a new ImageCacheConfig document for configuring the Image Cache feature, replacing the old machine.features.imageCache field in the v1alpha1 config.
Old configuration is still supported for backwards compatibility.
Talos introduces new multi-document configuration for kernel parameters (sysctl and sysfs settings), replacing the old v1alpha1 config fields.
The old configuration is still supported for backwards compatibility, but new deployments should use the new documents.
If both old and new configuration sources are used, the new multi-document configuration takes precedence over the old v1alpha1 config on conflicting fields.
List of changes:
.machine.sysctls in the v1alpha1 config; use the SysctlConfig document for kernel sysctl configuration..machine.sysfs in the v1alpha1 config; use the SysfsConfig document for sysfs configuration..machine.kernel in the v1alpha1 config; use the KernelModuleConfig document for kernel module configuration.Talos now reports the status of both dynamically loaded, and built-in kernel modules.
The LoadedKernelModule resource has been deprecated and superseded by the new KernelModuleStatus resource.
Because the kubelet now runs inside the sandbox namespace (see the workload isolation note), the in-tree
Kubernetes volume plugins that require the kubelet to reach host-level daemons no longer work. In particular
the in-tree iscsi volume plugin, which drives the kubelet's iscsiadm wrapper to talk to the host iscsid,
can no longer locate it across the sandbox PID namespace boundary.
Use CSI drivers instead — a CSI node plugin performs the attach/mount itself in its own privileged pod and is
unaffected by the sandbox. For iSCSI, kubernetes-csi/csi-driver-iscsi (or democratic-csi) consumes a
target the same way. All in-tree (non-CSI) volume plugins are deprecated for the kubelet and support for them
may be removed in a later release.
Talos introduces new multi-document Kubernetes configuration, which allows for more flexible and modular configuration of Kubernetes components.
Talos still supports the old v1alpha1 config for backwards compatibility, but new features and fields will only be available in the new multi-document format.
The kube-proxy is now using configuration to manage its settings instead of command line arguments (with new KubeProxyConfig document).
List of changes:
.cluster.secretboxEncryptionSecret in the v1alpha1 config; use the KubeEtcdEncryptionConfig document for full etcd encryption configuration..cluster.apiServer in the v1alpha1 config; use the KubeAPIServerConfig, KubeAdmissionControlConfig, KubeAuditPolicyConfig, KubeAuthenticationConfig and KubeAuthorizerConfig documents for kube-apiserver configuration..cluster.ca, .cluster.acceptedCAs and .cluster.aggregatorCA in the v1alpha1 config; use the KubeAPIServerCAConfig, KubeAggregatorCAConfig documents..cluster.controllerManager in the v1alpha1 config; use the KubeControllerManagerConfig document for kube-controller-manager configuration..cluster.scheduler in the v1alpha1 config; use the KubeSchedulerConfig document for kube-scheduler configuration..cluster.proxy in the v1alpha1 config; use the KubeProxyConfig document for kube-proxy configuration..cluster.network in the v1alpha1 config; use the KubeNetworkConfig document for Kubernetes network configuration; Flannel can be configured using the KubeFlannelCNIConfig document..cluster.coreDNS in the v1alpha1 config; use the KubeCoreDNSConfig document for CoreDNS configuration..cluster.name and .cluster.controlPlane.endpoint in the v1alpha1 config; use the KubeClusterConfig` document for cluster name and control plane endpoint configuration..cluster.allowSchedulingOnControlPlanes.machine.kubelet.skipNodeRegistration.machine.kubelet.registerWithFQDN.machine.kubelet.nodeIP.machine.nodeLabels.machine.nodeAnnotations.machine.nodeTaintsNoSchedule taint for controlplane and label are now explicitly listed in KubeNodeConfig..machine.kubelet fields in the v1alpha1 config; use the KubeNodeConfig and KubeCredentialProviderConfig documents for kubelet configuration..machine.pods in the v1alpha1 config; use the KubeStaticPodConfig document for static pod configuration..machine.files in the v1alpha1 config; use dedicated configuration documents such as EtcFileConfig and CRICustomizationConfig instead..machine.baseRuntimeSpecOverrides in the v1alpha1 config; use the CRIBaseRuntimeSpecConfig document for base runtimespec overrides..cluster.inlineManifests in the v1alpha1 config; use the KubeInlineManifestConfig document for inline manifests..cluster.extraManifests and .cluster.extraManifestHeaders in the v1alpha1 config; use the KubeExternalManifestConfig document for external manifests..machine.features.kubePrism; use the KubePrismConfig document for KubePrism configuration (or remove it to disable KubePrism)..machine.features.kubernetesTalosAPIAccess; use the KubeTalosAPIAccessConfig document instead.nodeCIDRMaskSizeIPv4 (default 24) and nodeCIDRMaskSizeIPv6 (default 64) settings to the KubeNetworkConfig document to control the per-node pod CIDR mask size and validate the pod and service subnet sizes.Secure Boot images no longer have lockdown=confidentiality enabled by default.
This change was made to improve compatibility with eBPF tooling under default schematic.
This means that Secure Boot images will now have lockdown=integrity enabled by default (implicitly), which is the recommended setting for most users.
Users can override it by adding lockdown=confidentiality to the kernel command line through Image Factory if they require it.
Logical volumes can now be declared with a new LVMLogicalVolumeConfig multi-doc config kind. Each document
names a logical volume, its parent volumeGroup, a type (linear, raid0, raid1 or raid10) and a
maxSize (absolute, e.g. 50GiB, or a percentage of the volume group, e.g. 80%). RAID layouts accept
optional mirrors (raid1/raid10, default 1) and stripes (raid0/raid10, default: all available physical
volumes) fields. Once the volume group is assembled the logical volume is created via lvcreate.
Raising maxSize grows an existing logical volume via lvextend; percentage-sized volumes also grow when
their volume group is extended. Shrinking is never performed (it risks data loss) - a request to reduce the
size surfaces an LVMValidationError instead. Removal stays an explicit operation via the LVMService LV
remove RPC (talosctl wipe lv).
Talos now provides detailed LVM status information, allowing for better monitoring and management of LVM volumes.
New resources LVMPhysicalVolumeStatus, LVMVolumeGroupStatus, and LVMLogicalVolumeStatus expose PV, VG, and LV details.
DiscoveredVolume resources for logical volumes are listed by their kernel name (e.g. dm-0). To resolve the <vg>/<lv> for a given device, use the Disks or BlockSymlinks resources, which carry the udev-managed symlinks (e.g. /dev/disk/by-id/dm-name-<vg>-<lv>).
Talos can now create and grow LVM Volume Groups declaratively through a new LVMVolumeGroupConfig multi-doc
config kind. Each document names a Volume Group and a CEL volumeSelector over the disk inventory; matched
disks are initialised as Physical Volumes (pvcreate) and aggregated into the requested VG (vgcreate).
Newly matched disks added to an existing VG are attached via vgextend.
Reconciliation is strictly additive and safe-by-default.
Talos now provides the ability to securely wipe LVM metadata from logical volumes, volume groups, and physical volumes.
This feature allows for selective wiping of logical volumes, volume groups, and physical volumes.
With talosctl wipe lv/vg/pv <name>, users can wipe LVM metadata from a specific logical volume, volume group, or physical volume.
Talos now supports Network Time Security (NTS) for secure time synchronization.
This feature enhances the security of NTP by providing cryptographic authentication of time sources.
NTS is enabled by default (without any configuration sources) for the default time.cloudflare.com time server
NTS can be enabled for custom time servers via the new useNTS field in the TimeServerConfig document.
Talos can now create and grow Linux MD (software RAID) arrays declaratively through a new RAIDArrayConfig
multi-doc config kind. Each document names an array, its level (raid1) and a CEL volumeSelector over
the disk inventory; matched disks are assembled into the requested array with mdadm and exposed at the stable
/dev/disk/by-id/md-name-<name> path. New matching disks added to an existing array are attached automatically.
Reconciliation is strictly additive and safe-by-default. Arrays are never destroyed by removing the config;
removal stays an explicit operation via talosctl wipe md <device>. The new MDArrayStatus resource reports the
assembled array, level, device path, and members.
Talos can now be installed onto and boot from a Linux MD (software RAID) array. Define a RAIDArrayConfig for the
array and point the install disk selector (UnattendedInstallConfig) at the resulting /dev/disk/by-id/md-name-<name>
device.
Only raid1 arrays with metadata: "1.0" can be used for booting: the 1.0 format keeps its superblock at the end of
each member, so the partition table written to the array stays visible at the start of every disk, allowing the
firmware to boot from any member. metadata defaults to 1.0; other levels and metadata formats are not bootable.
The container runtime plane — CRI containerd, the kubelet, and all pods — now runs inside a dedicated PID and
mount namespace anchored by a new sandboxd service, instead of sharing machined's namespaces.
sandboxd runs in its own least-privilege SELinux domain (sandboxd_t). if it dies the kernel tears down the
namespace and Talos recreates it — relaunching CRI, the kubelet, and pods — without rebooting the node.
Its logs are available via talosctl logs sandboxd.
Workload isolation is controlled by the workloadIsolation field of the new SecurityProfileConfig document.
talosctl gen config emits it with workloadIsolation: true for Talos 1.14+, so new clusters are isolated by
default. Clusters upgraded from older versions do not have this document and therefore keep the previous
(non-isolated) behavior until it is added — upgrades change nothing on their own. To enable on an existing
cluster, add the document:
apiVersion: v1alpha1
kind: SecurityProfileConfig
workloadIsolation: trueNOTE: With workload isolation enabled, the deprecated in-tree Kubernetes iSCSI volume plugin does not work
(the kubelet cannot reach the hostiscsidacross the sandbox); use a CSI driver instead. See the in-tree
volume plugin deprecation note.
Talos now sets net.ipv4.conf.all.send_redirects=0 and net.ipv4.conf.default.send_redirects=0 by default,
preventing the node from emitting ICMP redirect messages. This aligns with CIS Benchmark recommendations and
does not affect normal Kubernetes pod or service traffic. Nodes that deliberately act as L3 gateways relying
on ICMP redirects can override this via machine.sysctls.
The talosctl support command now encrypts support bundles using the age encryption tool, enhancing the security of support data.
The default set of recipients includes the 'siderolabs' GitHub organization members, but it can be overridden with custom recipients.
The ETCD, CRI, KUBELET and LOG system volumes (/var/lib/etcd, /var/lib/containerd, /var/lib/kubelet and /var/log)
can now be placed on dedicated partitions via a VolumeConfig document with provisioning set (optionally encrypted).
By default they remain directories under the EPHEMERAL volume.
ETCD and LOG volumes are mounted with noexec in addition to nosuid and nodev when secure: true is set.
apiVersion: v1alpha1
kind: VolumeConfig
name: ETCD
provisioning:
minSize: 1GB
maxSize: 2GBThe backing (directory vs. dedicated partition) is fixed at cluster creation: switching an already-provisioned node between the two is rejected.
A dedicated partition has its own mount, so the mount.secure option (nosuid/nodev, enabled by default) can be set per volume; directory-backed volumes inherit the EPHEMERAL mount options. Talos additionally applies noexec to dedicated ETCD and LOG volumes, while CRI and KUBELET remain executable.
Note that with ETCD on a dedicated partition, etcd data no longer lives under EPHEMERAL. Resetting a control plane node with only the EPHEMERAL partition wiped will not clear etcd data; wipe the ETCD volume to reset etcd.
Talos now runs etcd and kube-apiserver with a minimum TLS version of 1.3, improving security by leveraging the latest TLS features and cipher suites.
Custom settings for cipher suites have been removed, as they are ignored when TLS 1.3 is used, which simplifies configuration and ensures the use of modern, secure defaults.
Talos introduces new multi-document configuration UdevRulesConfig document for configuring custom udev rules.
The old v1alpha1 .machine.udev.rules field is still supported for backwards compatibility, but new deployments should use the new document.
If both old and new configuration sources are used, UdevRulesConfig takes precedence.
List of changes:
.machine.udev.rules in the v1alpha1 config; use the UdevRulesConfig document for custom udev rules.Talos introduces a new UnattendedInstall multi-document config kind which replaces the deprecated .machine.install
section of the v1alpha1 config. The document carries the installer image and a provisioning section with a CEL
volumeSelector to match the install disk, plus a wipe option.
When the UnattendedInstall document is present, the install is driven by the new UnattendedInstallController
(exposing an UnattendedInstallStatus resource) instead of the legacy install sequence.
talosctl gen config and talosctl cluster create now generate the UnattendedInstall document by default.
The .machine.install field remains supported for backwards compatibility and is still used for older version contracts.
Linux: 6.18.46
Kubernetes: 1.37.0-rc.1
containerd: 2.3.4
etcd: 3.7.1
Flannel: 0.28.9
runc: 1.5.1
CoreDNS: 1.14.7
Talos is built with Go 1.26.7.
Talos now supports declarative virtual Ethernet (veth) pairs through the new VethConfig multi-document
configuration kind. Both endpoints are created in the host network namespace and support the common link settings,
addresses, routes, and multicast configuration.
For example, the following configuration creates a pair named veth-host and veth-router with an address on each
endpoint:
apiVersion: v1alpha1
kind: VethConfig
name: veth-host
addresses:
- address: 10.3.0.1/30
peer:
name: veth-router
addresses:
- address: 10.3.0.2/30On non-rotational devices mkfs.xfs sizes the allocation group count to the number of CPUs, bounding the
allocation group size from below at 4 GiB only. On machines with many cores and a modest disk this produces
hundreds of tiny allocation groups, which squeezes the AG-local reflink/rmap metadata (leading to spurious
ENOSPC on reflink-heavy workloads while the filesystem still has plenty of free space) and inflates the
journal at the same time.
Talos now keeps XFS allocation groups at 64 GiB or above when it formats a volume. The bound can be changed
per volume, and setting it to zero restores the stock mkfs.xfs behavior:
apiVersion: v1alpha1
kind: VolumeConfig
name: EPHEMERAL
filesystem:
xfs:
minAllocationGroupSize: 128GiBThe same filesystem.xfs.minAllocationGroupSize setting is available for UserVolumeConfig.
Note: allocation group geometry is fixed when the filesystem is created, so this only affects volumes
formatted by Talos 1.14 or later. Existing volumes keep their current geometry until they are wiped and
re-created (e.g. talosctl reset --system-labels-to-wipe=EPHEMERAL).
Talos now supports automatically running background online filesystem maintenance tasks. Currently,
only XFS using xfs_scrub tool is supported.
This behavior can be enabled globally using a FilesystemScrubConfig document, or on per-volume
basis using a field in corresponding VolumeConfig documents.
noexec for KUBELET, EPHEMERAL and CRINote truncated.
One column per quarter.
52 commits
9abd05af4 release(v1.14.0): prepare release
ff772d64f chore: mark release as stable
5424dac73 test: relax OOM test conditions
9f6719422 fix: normalize image reference when passing to image verification flow
6ce58d308 fix: name diskSelector in UnattendedInstallConfig validation errors
af4e11b50 test: isolate base OCI spec test in BGP CLOS runs
ff56b6d66 chore: update tools and pkgs
8c8b9b45f fix: filter the output in talosctl
9777a1bb4 feat: talos containers run with imagegccontroller
dd566c9c7 fix: container mount rshared propagation
2f8931768 refactor: don't skip container tests in short mode
2f0fdd11e fix: ctr machinedaccss allowed roles
64aef9053 feat: containers can connect to machined
ce2148aa0 feat: impl. container mount controller
9105c5e1e feat: talos containers support for talosctl
36fd44677 feat: impl. container runtime controller
afc09d418 refactor: make runner.runner context-native
eff936cf0 feat: impl ContainerInstanceController
95abc8bff fix: filter out passed metadata in API proxying
10c4f1a8b fix: treat desired roles empty as error in Talos API access
807b692a1 fix: allow CSI volumes to be mounted with an SELinux context
6249f3f4e test: skip filemap heap test under race detector
87a031b7f test: libvirtd extensions
e8b376365 fix: validate received kubeconfig
abce4c937 fix: use os.Root in the talosctl extract path
1deae73dd fix: escape output in the talosctl dashboard
5b153233c chore: speed up unit-tests
3715ce908 fix: add checks for meta key in the API path
138958053 feat: update COSI to 1.16.3
bdc7f3053 fix: preserve shared libs symlinks
7366edc90 chore: reduce verbosity of the grype scan
c027a947f fix: exclude scheduler config from apiserver config version
544fc52cb feat: add host extension pre-shutdown hooks
1d911581d fix: route creation churning every 100ms
baca68d0d fix: drop dead legacy registries init from worker generation
dec9dc3dc chore: bump sigstore/rekor to v1.5.4
dc9e7fea9 chore: add SPD5118 driver to squashfs
ae4d8228e fix: keep the time sync boot timeout across a syncer restart
755900fcc fix: preserve special modes when extracting files
6c927a0ff fix: hostns etc mount
3cdd0e748 feat: bump kubernetes to 1.37.0
03c567929 refactor: log filter stays enabled on enter press
b690b7ad5 fix: write the uploaded etcd snapshot atomically
25a366162 chore: update multipath notes
866db94f1 fix: drop gRPC client keepalive aggressive settings in the tracker
74e88bd57 feat: support host extension services
e828fe80a fix: skip selinux label for read-only/detached/external mounts
1be6787a5 fix: capture packets correctly on VLANs
d16d765f7 docs: update CRI customization example
1b31e1213 fix: use os.Root in the untar path
91a6af032 fix: enable additional SELinux permissions for Cilium
322de8bf2 fix: cache filemap layers on disk
Your coding agent can read these notes before it upgrades. Set up the MCP server →