github rancher/rke2 v1.22.15+rke2r1

12 months ago

This release updates Kubernetes to v1.22.15, fixes a number of minor issues, and includes security updates.
Important Note

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:

cat /var/lib/rancher/rke2/server/token

Changes since v1.22.13+rke2r1:

  • [Release 1.22] Update Cilium version (#3281)
  • [Release 1.22] Bump the cilium chart version (#3294)
  • [Release 1.22] Update canal version (#3287)
  • The bundled version of runc has been bumped to v1.1.4 (#3303)
  • update to latest 1.22 patch (#3349)
  • Update k8s to 1.22.15 (#3372)

Packaged Component Versions

Component Version
Kubernetes v1.22.15
Etcd v3.5.4
Containerd v1.5.13-k3s1
Runc v1.1.4
Metrics-server v0.5.0
CoreDNS v1.9.3
Ingress-Nginx 4.1.0
Helm-controller v0.12.3

Available CNIs

Component Version FIPS Compliant
Canal (Default) Flannel v0.19.1
Calico v3.21.5
Yes
Calico v3.21.5 No
Cilium v1.12.1 No
Multus v3.8 No

Known Issues

  • #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.22.15+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

Helpful Links

As always, we welcome and appreciate feedback from our community of users. Please feel free to:

Don't miss a new rke2 release

NewReleases is sending notifications on new releases.