This release updates Kubernetes to v1.23.16 to backport registry changes and fix two critical issues.
If your server (control-plane) nodes were not started with the
--token CLI 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.23.15+rke2r1:
- Generate report and upload test results (#3771) (#3796)
- Bump harvester cloud provider and harvester csi driver (#3783)
- Bump K3s version for tls-cipher-suites fix (#3797)
- Bump vSphere CPI chart to v1.23.3 (#3807)
- Update to v1.23.16 (#3809)
- Bump containerd to v1.5.16-k3s2 (#3831)
- The embedded containerd version has been bumped to v1.5.16-k3s2. This includes a backported fix for containerd/7843 which caused pods to lose their CNI info when containerd was restarted, which in turn caused the kubelet to recreate the pod.
- Windows agents now use the k3s fork of containerd, which includes support for registry rewrites.
Packaged Component Versions
|Canal (Default)||Flannel v0.20.2|
- #1447 - When restoring RKE2 from backup to a new node, you should ensure that all pods are stopped following the initial restore:
curl -sfL https://get.rke2.io | sudo INSTALL_RKE2_VERSION=v1.23.16+rke2r1 rke2 server \ --cluster-reset \ --cluster-reset-restore-path=<PATH-TO-SNAPSHOT> --token <token used in the original cluster> rke2-killall.sh systemctl enable rke2-server systemctl start rke2-server
As always, we welcome and appreciate feedback from our community of users. Please feel free to: