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
Copy file name to clipboardExpand all lines: asciidoc/edge-book/releasenotes.adoc
+178-3Lines changed: 178 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,181 @@ However, repeated entries are provided as a courtesy only. Therefore, if you are
32
32
33
33
NOTE: SUSE Edge z-stream releases are tightly integrated and thoroughly tested as a versioned stack. Upgrade of any individual components to a different versions to those listed above is likely to result in system downtime. While it's possible to run Edge clusters in untested configurations, it is not recommended, and it may take longer to provide resolution through the support channels.
34
34
35
+
[#release-notes-3-4-3]
36
+
= Release 3.4.3
37
+
38
+
Availability Date: 12th January 2026
39
+
40
+
Full Support End Date: 20th March 2026
41
+
42
+
Maintenance Support End Date: 20th September 2027
43
+
44
+
EOL: 21st September 2027
45
+
46
+
Summary: SUSE Edge 3.4.3 is the third z-stream release in SUSE Edge 3.4 release stream
47
+
48
+
== New Features
49
+
50
+
* Updated to Kubernetes 1.33.6 and Rancher Prime 2.12.5 https://github.com/rancher/rancher/releases/tag/v2.12.5[Release Notes]
51
+
* Update to SUSE Multi-Linux Manager 5.0.6 https://documentation.suse.com/releasenotes/suma/5.0/#_version_5_0_6[Release Notes)
52
+
53
+
== Bug & Security Fixes
54
+
55
+
* The Edge Rancher Turtles chart has been updated to ensure resources are correctly removed on uninstallation (which will be required as part of the migration for upgrade to 3.5)
56
+
* RKE2 1.33.6 contains several version updates and fixes https://github.com/rancher/rke2/releases/tag/v1.33.6%2Brke2r1[Release Notes]
57
+
* SUSE Multi-Linux Manager 5.0.6 contains several security related fixes https://documentation.suse.com/releasenotes/suma/5.0/#_version_5_0_6[Release Notes)
58
+
59
+
== Known Issues
60
+
61
+
[WARNING]
62
+
====
63
+
If deploying new clusters, please follow <<guides-kiwi-builder-images>> to build fresh images first as this is now the first step required to create clusters for both {x86-64} and {aarch64} architectures as well as management and downstream clusters.
64
+
====
65
+
66
+
* When deploying via Edge Image Builder, `HelmChartConfigs` manifests may fail if they are put in the `kubernetes/manifests` configuration directory. Instead it is reccomended to place any `HelmChartConfigs` in `/var/lib/rancher/{rke2/k3s}/server/manifests/` using the EIB os-files interface, see <<mgmt-cluster-directory-structure>> for example. Failure to do this may cause nodes to stay in `NotReady` state on initial startup, as discussed in https://github.com/rancher/rke2/issues/8357[#8357 RKE2 issue]
67
+
68
+
* On RKE2/K3s 1.31, 1.32 and 1.33 versions, the directory `/etc/cni` being used to store CNI configurations may not trigger a notification of the files being written there to `containerd` due to certain conditions related to `overlayfs` (see the https://github.com/rancher/rke2/issues/8356[#8356 RKE2 issue]). This in turn results in the deployment of RKE2/K3s to get stuck waiting for the CNI to start, and the RKE2/K3s nodes to stay in `NotReady` state. This can be seen at node level with `kubectl describe node <affected_node>`:
69
+
70
+
[,bash]
71
+
----
72
+
Conditions:
73
+
Type Status LastHeartbeatTime LastTransitionTime Reason Message
Ready False Thu, 05 Jun 2025 17:41:28 +0000 Thu, 05 Jun 2025 14:38:16 +0000 KubeletNotReady container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized
76
+
----
77
+
78
+
As a workaround, a tmpfs volume can be mounted at the `/etc/cni` directory before RKE2 starts. It avoids the usage of overlayfs which results in containerd missing notifications and the configs should get rewritten every time the node is restarted and the pods initcontainers run again. If using EIB, this can be a `04-tmpfs-cni.sh` script in the `custom/scripts` directory (as explained here[https://github.com/suse-edge/edge-image-builder/blob/release-1.2/docs/building-images.md#custom]) that looks like:
79
+
80
+
[,bash]
81
+
----
82
+
#!/bin/bash
83
+
mkdir -p /etc/cni
84
+
mount -t tmpfs -o mode=0700,size=5M tmpfs /etc/cni
* When onboarding remote hosts using Elemental, a race condition between `dbus.service` and `elemental-system-agent.service` might occur, resulting in `rancher-system-agent.service` on remote host to fail starting with errors similar to the one below. (see the https://github.com/suse-edge/edge-image-builder/issues/784[#784 Edge Image Builder issue] for details.)
89
+
90
+
[,bash]
91
+
----
92
+
Sep 19 19:38:07 elementalvm elemental-system-agent[3671]: time="2025-09-19T19:38:07Z" level=info msg="[6b20fe64c854da2639804884b34129bb8f718eb59578111da58d9de1509c24db_1:stderr]: Failed to restart rancher-system-agent.service: Message recipient disconnected from message bus without replying"
93
+
----
94
+
95
+
As a workaround, a systemd override file can be created as below
ExecStartPre=/bin/bash -c 'echo "Waiting for dbus to become active..." | systemd-cat -p info -t elemental-system-agent; sleep 15; timeout 300 bash -c "while ! systemctl is-active --quiet dbus.service; do sleep 15; done"'
105
+
----
106
+
107
+
and a custom script named `30a-copy-elemental-system-agent-override.sh` can be used to place the override to `/etc/systemd/system/elemental-system-agent.service.d` prior to EIB's https://github.com/suse-edge/edge-image-builder/blob/main/pkg/combustion/templates/31-elemental-register.sh.tpl[31-elemental-register.sh] script runs during the combustion phase.
The following table describes the individual components that make up the 3.4.3 release, including the version, the Helm chart version (if applicable), and from where the released artifact can be pulled in the binary format. Please follow the associated documentation for usage and deployment examples.
120
+
121
+
|======
122
+
| Name | Version | Helm Chart Version | Artifact Location (URL/Image)
123
+
| SUSE Linux Micro | 6.1 (latest) | N/A | https://www.suse.com/download/sle-micro/[SUSE Linux Micro Download Page] +
@@ -122,7 +297,7 @@ and a custom script named `30a-copy-elemental-system-agent-override.sh` can be u
122
297
123
298
== Component Versions
124
299
125
-
The following table describes the individual components that make up the 3.4.1 release, including the version, the Helm chart version (if applicable), and from where the released artifact can be pulled in the binary format. Please follow the associated documentation for usage and deployment examples.
300
+
The following table describes the individual components that make up the 3.4.2 release, including the version, the Helm chart version (if applicable), and from where the released artifact can be pulled in the binary format. Please follow the associated documentation for usage and deployment examples.
126
301
127
302
|======
128
303
| Name | Version | Helm Chart Version | Artifact Location (URL/Image)
0 commit comments