This release is RKE2's first in the v1.28 line. This release updates Kubernetes to v1.28.1.
Before upgrading from earlier releases, be sure to read the Kubernetes Urgent Upgrade Notes.
⚠️ This release includes remediation for CVE-2023-32186, a potential Denial of Service attack vector on RKE2 servers. See GHSA-p45j-vfv5-wprq for more information, including documentation on changes in behavior that harden clusters against this vulnerability.
Kubernetes v1.28 contains a critical regression (kubernetes/kubernetes#120247) that causes init containers to run at the same time as app containers following a restart of the node. This issue will be fixed in v1.28.2. We do not recommend using RKE2 v1.28 at this time.
If your server (control-plane) nodes were not started with the
--tokenCLI flag or config file key, a randomized token was generated during initial cluster startup. This key is used both for joining new nodes to the cluster, and for encrypting cluster bootstrap data within the datastore. Ensure that you retain a copy of this token, as is required when restoring from backup.
You may retrieve the token value from any server already joined to the cluster:
Changes since v1.27.5+rke2r1:
- Add additional static pod cleanup during cluster reset (#4712)
- Bump k3s and kubernetes versions for v1.28 (#4705)
Packaged Component Versions
|Canal (Default)||Flannel v0.22.1|
As always, we welcome and appreciate feedback from our community of users. Please feel free to: